It is generally recommended to explicitly declare the visibility for methods.
Adding explicit visibility (private, protected, or public) is generally
recommend to communicate to other developers how, and from where this method
is intended to be used.
Loading history...
16
{
17
$this->builder = $builder;
18
}
19
20
public function getFunctions()
21
{
22
return array(
23
new Twig_SimpleFunction('alpixel_get_menu', array($this, 'get')),
The class Twig_SimpleFunction has been deprecated with message: to be removed in 3.0
This class, trait or interface has been deprecated. The supplier of the file has supplied an explanatory message.
The explanatory message should give you some clue as to whether and when the type will be
removed from the class and what other constant to use instead.
Loading history...
24
new Twig_SimpleFunction('alpixel_render_menu', array($this, 'render'), array(
The class Twig_SimpleFunction has been deprecated with message: to be removed in 3.0
This class, trait or interface has been deprecated. The supplier of the file has supplied an explanatory message.
The explanatory message should give you some clue as to whether and when the type will be
removed from the class and what other constant to use instead.
Both the $myVar assignment in line 1 and the $higher assignment in line 2
are dead. The first because $myVar is never used and the second because
$higher is always overwritten for every possible time line.
Adding explicit visibility (
private
,protected
, orpublic
) is generally recommend to communicate to other developers how, and from where this method is intended to be used.