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.
The class Bitsy_Wrapping is not named in CamelCase.
This check marks class names that have not been written 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 connector becomes DatabaseConnector.
The property $main_template is not named in camelCase.
This check marks property names that have not been 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 string becomes databaseConnectionString.
Loading history...
22
23
/**
24
* Stores the full path to the main template file
25
*/
26
static $main_template;
27
28
/**
29
* Stores the base name of the template file; e.g. 'page' for 'page.php' etc.
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.
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.
The variable $main_template is not named in camelCase.
This check marks variable names that have not been 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 string becomes databaseConnectionString.
sewmyheadon /
bitsy
Loading history...
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
@returnannotation as described here.