Completed
Branch master (cd0f1c)
by Michael
03:21
created

getDebugInfo()   A

Complexity

Conditions 1
Paths 1

Size

Total Lines 4
Code Lines 2

Duplication

Lines 0
Ratio 0 %

Importance

Changes 1
Bugs 0 Features 1
Metric Value
c 1
b 0
f 1
dl 0
loc 4
rs 10
cc 1
eloc 2
nc 1
nop 0
1
<?php
2
3
/* index.twig */
4
class __TwigTemplate_62f4867098898f39fbfee89942bb9a2bc59a998c5556371af91ab477e245843f extends Twig_Template
0 ignored issues
show
Coding Style Compatibility introduced by
PSR1 recommends that each class must be in a namespace of at least one level to avoid collisions.

You can fix this by adding a namespace to your class:

namespace YourVendor;

class YourClass { }

When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries.

Loading history...
Coding Style introduced by
This class is not in CamelCase format.

Classes in PHP are usually named in CamelCase.

In camelCase names are written without any punctuation, the start of each new word being marked by a capital letter. The whole name starts with a capital letter as well.

Thus the name database provider becomes DatabaseProvider.

Loading history...
5
{
6
    public function __construct(Twig_Environment $env)
7
    {
8
        parent::__construct($env);
9
10
        $this->blocks = array(
11
            'body_class' => array($this, 'block_body_class'),
12
        );
13
    }
14
15
    protected function doGetParent(array $context)
0 ignored issues
show
Documentation introduced by
The return type could not be reliably inferred; please add a @return annotation.

Our type inference engine in quite powerful, but sometimes the code does not provide enough clues to go by. In these cases we request you to add a @return annotation as described here.

Loading history...
16
    {
17
        // line 7
18
        return $this->loadTemplate((isset($context["extension"]) ? $context["extension"] : $this->getContext($context, "extension")), "index.twig", 7);
19
    }
20
21
    protected function doDisplay(array $context, array $blocks = array())
22
    {
23
        // line 1
24
        if ((isset($context["has_namespaces"]) ? $context["has_namespaces"] : $this->getContext($context, "has_namespaces"))) {
25
            // line 2
26
            $context["extension"] = "namespaces.twig";
27
        } else {
28
            // line 4
29
            $context["extension"] = "classes.twig";
30
        }
31
        // line 7
32
        $this->getParent($context)->display($context, array_merge($this->blocks, $blocks));
33
    }
34
35
    // line 9
36
    public function block_body_class($context, array $blocks = array())
0 ignored issues
show
Coding Style introduced by
This method is not in camel caps format.

This check looks for method names that are not written in camelCase.

In camelCase names are written without any punctuation, the start of each new word being marked by a capital letter. Thus the name database connection seeker becomes databaseConnectionSeeker.

Loading history...
37
    {
38
        echo "index";
39
    }
40
41
    public function getTemplateName()
42
    {
43
        return "index.twig";
44
    }
45
46
    public function isTraitable()
47
    {
48
        return false;
49
    }
50
51
    public function getDebugInfo()
52
    {
53
        return array (  36 => 9,  32 => 7,  29 => 4,  26 => 2,  24 => 1,  18 => 7,);
54
    }
55
}
56
/* {% if has_namespaces %}*/
57
/*     {% set extension = 'namespaces.twig' %}*/
58
/* {% else %}*/
0 ignored issues
show
Unused Code Comprehensibility introduced by
38% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
59
/*     {% set extension = 'classes.twig' %}*/
60
/* {% endif %}*/
0 ignored issues
show
Unused Code Comprehensibility introduced by
38% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
61
/* */
62
/* {% extends extension %}*/
63
/* */
64
/* {% block body_class 'index' %}*/
65
/* */
66