These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
1 | <?php |
||
0 ignored issues
–
show
|
|||
2 | /** |
||
3 | * Tests.php |
||
4 | * @ignore |
||
5 | */ |
||
6 | namespace w3l\Holt45\Tests; |
||
7 | |||
8 | require_once dirname(__FILE__) . '/holt45.php'; |
||
9 | |||
10 | class Tests extends \Holt45 |
||
11 | { |
||
12 | public function allTests() |
||
13 | { |
||
14 | /* $_GET */ |
||
15 | if (self::chkGet("q")) { |
||
16 | echo '$_GET["q"] is set'; |
||
17 | } |
||
18 | |||
19 | echo self::assignFromGet("q"); // "" or $_GET["q"] |
||
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
67% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. ![]() |
|||
20 | |||
21 | if (self::chkGetAll(array("q", "search"))) { |
||
22 | echo '$_GET["q"] and $_GET["search"] is set'; |
||
23 | } |
||
24 | |||
25 | /* $_POST */ |
||
26 | if (self::chkPost("q")) { |
||
27 | echo '$_POST["q"] is set'; |
||
28 | } |
||
29 | |||
30 | echo self::assignFromPost("q"); // "" or $_POST["q"] |
||
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
67% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. ![]() |
|||
31 | |||
32 | if (self::chkPostAll(array("q", "search"))) { |
||
33 | echo '$_POST["q"] and $_POST["search"] is set'; |
||
34 | } |
||
35 | |||
36 | /* Sessions */ |
||
37 | self::sessionSet("example_session_name", "content of session", 86400); |
||
38 | |||
39 | if (self::sessionIsset("example_session_name")) { |
||
40 | echo 'Session example_session_name is set and not expired'; |
||
41 | } |
||
42 | |||
43 | echo self::sessionRead("example_session_name"); // content of session |
||
44 | |||
45 | self::sessionDelete("example_session_name"); // Deletes session |
||
46 | |||
47 | /* Time */ |
||
48 | echo self::timestampToHttpDate("1980-01-01 17:15:00"); // Tue, 01 Jan 1980 16:15:00 GMT |
||
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
48% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. ![]() |
|||
49 | |||
50 | echo self::timeElapsed("1980-01-01 17:15:00"); // 13173 days |
||
51 | |||
52 | /* Convert */ |
||
53 | echo self::rgbhex(array(255, 0, 0)); // ff0000 |
||
54 | |||
55 | print_r(self::hexrgb("#FF0000")); // Array([0] => 255, [1] => 0, [2] => 0) |
||
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
69% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. ![]() |
|||
56 | |||
57 | /* Strings */ |
||
58 | echo self::textareaEncode('<textarea id="tex1"></textarea> <p> asdasd </p>'); // [textarea id="tex1"][/textarea] <p> asdasd </p> |
||
0 ignored issues
–
show
|
|||
59 | |||
60 | echo self::textareaDecode('[textarea id="tex1"][/textarea] <p> asdasd </p>'); // <textarea id="tex1"></textarea> <p> asdasd </p> |
||
0 ignored issues
–
show
|
|||
61 | |||
62 | echo self::obfuscateString("Hi, I'm a ninja!"); // 49574671626d6c75494745676253644a4943787053413d3d |
||
63 | |||
64 | echo self::deobfuscateString("49574671626d6c75494745676253644a4943787053413d3d"); // Hi, I'm a ninja! |
||
65 | |||
66 | echo self::replaceString("Hi my name is [@foo] and i like [@bar]", array("foo" => "sven", "bar" => "beer")); // Hi my name is sven and i like beer |
||
0 ignored issues
–
show
|
|||
67 | |||
68 | echo self::rainbowText("Hallo world"); // <span style="color: #ff0000;">H</span><span style="color: #ff3300;">a</span>... |
||
0 ignored issues
–
show
|
|||
69 | |||
70 | /* Math */ |
||
71 | print_r(self::generatePaginationRange(106, 15, 7)); // Array([0] => 1, [1] => 13, [2] => 14, [3] => 15, [4] => 16, [5] => 17, [6] => 106) |
||
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
68% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. ![]() |
|||
72 | |||
73 | /* Misc */ |
||
74 | echo self::getClientIpAddress(); // 127.0.0.1 |
||
75 | |||
76 | print_r(self::urlParser("htt://w.google..com/")); // Array([url] => http://www.google.com/, [url_display] => www.google.com) |
||
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
70% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. ![]() |
|||
77 | |||
78 | echo self::generatePassword(10); // 2k%=cbot:w |
||
79 | |||
80 | echo self::generatePassword(10, "simple"); // m9b7gfkmhc |
||
81 | |||
82 | echo self::iso3166ToName("SE"); // SWEDEN |
||
83 | |||
84 | /* constants */ |
||
85 | echo self::DATA_URI_TRANSPARENT_GIF; // data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7 |
||
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
45% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. ![]() |
|||
86 | |||
87 | echo self::DATA_URI_TRANSPARENT_PNG; // data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAQAAAC1HAwCAAAAC0lEQVQYV2NgYAAAAAMAAWgmWQ0AAAAASUVORK5CYII= |
||
0 ignored issues
–
show
|
|||
88 | } |
||
89 | } |
||
90 |
The PSR-1: Basic Coding Standard recommends that a file should either introduce new symbols, that is classes, functions, constants or similar, or have side effects. Side effects are anything that executes logic, like for example printing output, changing ini settings or writing to a file.
The idea behind this recommendation is that merely auto-loading a class should not change the state of an application. It also promotes a cleaner style of programming and makes your code less prone to errors, because the logic is not spread out all over the place.
To learn more about the PSR-1, please see the PHP-FIG site on the PSR-1.