| Conditions | 1 | 
| Paths | 1 | 
| Total Lines | 72 | 
| Code Lines | 43 | 
| Lines | 0 | 
| Ratio | 0 % | 
| Changes | 0 | ||
Small methods make your code easier to understand, in particular if combined with a good name. Besides, if your method is small, finding a good name is usually much easier.
For example, if you find yourself adding comments to a method's body, this is usually a good sign to extract the commented part to a new method, and use the comment as a starting point when coming up with a good name for this new method.
Commonly applied refactorings include:
If many parameters/temporary variables are present:
| 1 | <?php | ||
| 38 | public function getBaseUrlData() | ||
| 39 |     { | ||
| 40 | return [ | ||
| 41 | [ | ||
| 42 | '/fruit/strawberry/1234index.php/blah', | ||
| 43 | [ | ||
| 44 | 'SCRIPT_FILENAME' => 'E:/Sites/cc-new/public_html/fruit/index.php', | ||
| 45 | 'SCRIPT_NAME' => '/fruit/index.php', | ||
| 46 | 'PHP_SELF' => '/fruit/index.php', | ||
| 47 | ], | ||
| 48 | '/fruit', | ||
| 49 | '/strawberry/1234index.php/blah', | ||
| 50 | ], | ||
| 51 | [ | ||
| 52 | '/fruit/strawberry/1234index.php/blah', | ||
| 53 | [ | ||
| 54 | 'SCRIPT_FILENAME' => 'E:/Sites/cc-new/public_html/index.php', | ||
| 55 | 'SCRIPT_NAME' => '/index.php', | ||
| 56 | 'PHP_SELF' => '/index.php', | ||
| 57 | ], | ||
| 58 | '', | ||
| 59 | '/fruit/strawberry/1234index.php/blah', | ||
| 60 | ], | ||
| 61 | [ | ||
| 62 | '/foo%20bar/', | ||
| 63 | [ | ||
| 64 | 'SCRIPT_FILENAME' => '/home/John Doe/public_html/foo bar/app.php', | ||
| 65 | 'SCRIPT_NAME' => '/foo bar/app.php', | ||
| 66 | 'PHP_SELF' => '/foo bar/app.php', | ||
| 67 | ], | ||
| 68 | '/foo%20bar', | ||
| 69 | '/', | ||
| 70 | ], | ||
| 71 | [ | ||
| 72 | '/foo%20bar/home', | ||
| 73 | [ | ||
| 74 | 'SCRIPT_FILENAME' => '/home/John Doe/public_html/foo bar/app.php', | ||
| 75 | 'SCRIPT_NAME' => '/foo bar/app.php', | ||
| 76 | 'PHP_SELF' => '/foo bar/app.php', | ||
| 77 | ], | ||
| 78 | '/foo%20bar', | ||
| 79 | '/home', | ||
| 80 | ], | ||
| 81 | [ | ||
| 82 | '/foo%20bar/app.php/home', | ||
| 83 | [ | ||
| 84 | 'SCRIPT_FILENAME' => '/home/John Doe/public_html/foo bar/app.php', | ||
| 85 | 'SCRIPT_NAME' => '/foo bar/app.php', | ||
| 86 | 'PHP_SELF' => '/foo bar/app.php', | ||
| 87 | ], | ||
| 88 | '/foo%20bar/app.php', | ||
| 89 | '/home', | ||
| 90 | ], | ||
| 91 | [ | ||
| 92 | '/foo%20bar/app.php/home%3Dbaz', | ||
| 93 | [ | ||
| 94 | 'SCRIPT_FILENAME' => '/home/John Doe/public_html/foo bar/app.php', | ||
| 95 | 'SCRIPT_NAME' => '/foo bar/app.php', | ||
| 96 | 'PHP_SELF' => '/foo bar/app.php', | ||
| 97 | ], | ||
| 98 | '/foo%20bar/app.php', | ||
| 99 | '/home%3Dbaz', | ||
| 100 | ], | ||
| 101 | [ | ||
| 102 | '/foo/bar+baz', | ||
| 103 | [ | ||
| 104 | 'SCRIPT_FILENAME' => '/home/John Doe/public_html/foo/app.php', | ||
| 105 | 'SCRIPT_NAME' => '/foo/app.php', | ||
| 106 | 'PHP_SELF' => '/foo/app.php', | ||
| 107 | ], | ||
| 108 | '/foo', | ||
| 109 | '/bar+baz', | ||
| 110 | ], | ||
| 120 | 
The issue could also be caused by a filter entry in the build configuration. If the path has been excluded in your configuration, e.g.
excluded_paths: ["lib/*"], you can move it to the dependency path list as follows:For further information see https://scrutinizer-ci.com/docs/tools/php/php-scrutinizer/#list-dependency-paths