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 string literal badges:leaderboard does not require double quotes, as per coding-style, please use single quotes.
PHP provides two ways to mark string literals. Either with single quotes 'literal' or with
double quotes "literal". The difference between these is that string literals in double quotes
may contain variables with are evaluated at run-time as well as escape sequences.
String literals in single quotes on the other hand are evaluated very literally and the only two
characters that needs escaping in the literal are the single quote itself (\') and the
backslash (\\). Every other character is displayed as is.
Double quoted string literals may contain other variables or more complex escape sequences.
<?php$singleQuoted='Value';$doubleQuoted="\tSingle is $singleQuoted";print$doubleQuoted;
will print an indented: SingleisValue
If your string literal does not contain variables or escape sequences, it should be defined
using single quotes to make that fact clear.
For more information on PHP string literals and available escape sequences see the PHP core
documentation.
The property content_type cannot be accessed from this context as it is declared private in class Wall.
This check looks for access to properties that are not accessible from the current context.
If you need to make a property accessible to another context you can either raise its
visibility level or provide an accessible getter in the defining class.
The property uid cannot be accessed from this context as it is declared private in class Wall.
This check looks for access to properties that are not accessible from the current context.
If you need to make a property accessible to another context you can either raise its
visibility level or provide an accessible getter in the defining class.
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.