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...
13
return SpursWrapping::$mainTemplate;
14
}
15
16
function spurs_template_base() {
17
return SpursWrapping::$base;
18
}
19
20
21
class SpursWrapping {
22
23
/**
24
* Stores the full path to the main template file
25
* @return string
26
*/
27
static $mainTemplate;
28
29
/**
30
* 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.
sewmyheadon /
spurs
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.