Kint_Parser_Timestamp does not seem to conform to the naming convention (^[A-Z][a-zA-Z0-9]*$).
This check examines a number of code elements and verifies that they conform
to the given naming conventions.
You can set conventions for local variables, abstract classes, utility classes, constant, properties,
methods, parameters, interfaces, classes, exceptions and special methods.
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...
18
{
19
return Kint_Parser::TRIGGER_SUCCESS;
20
}
21
22
public function parse(&$var, Kint_Object &$o, $trigger)
Avoid variables with short names like $o. Configured minimum length is 3.
Short variable names may make your code harder to understand. Variable names should
be self-descriptive. This check looks for variable names who are shorter than
a configured minimum.
Loading history...
23
{
24
if (is_string($var) && !ctype_digit($var)) {
25
return;
26
}
27
28
if (in_array($var, self::$blacklist)) {
29
return;
30
}
31
32
$len = strlen($var);
33
34
// Guess for anything between March 1973 and November 2286
35
if ($len === 9 || $len === 10) {
36
// If it's an int or string that's this short it probably has no other meaning
37
// Additionally it's highly unlikely the shortValue will be clipped for length
38
// If you're writing a plugin that interferes with this, just put your
39
// parser plugin further down the list so that it gets loaded afterwards.
kint-php /
kint
Loading history...
This check examines a number of code elements and verifies that they conform to the given naming conventions.
You can set conventions for local variables, abstract classes, utility classes, constant, properties, methods, parameters, interfaces, classes, exceptions and special methods.