DASPRiD /
Dash
| Conditions | 10 |
| Paths | 20 |
| Total Lines | 45 |
| Code Lines | 27 |
| Lines | 0 |
| Ratio | 0 % |
| Changes | 2 | ||
| Bugs | 0 | Features | 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 |
||
| 40 | public static function matchRouteCollection( |
||
| 41 | RouteCollectionInterface $routeCollection, |
||
| 42 | ServerRequestInterface $request, |
||
| 43 | $pathOffset, |
||
| 44 | array $parentParams |
||
| 45 | ) { |
||
| 46 | $methodFailureResult = null; |
||
| 47 | $schemeFailureResult = null; |
||
| 48 | |||
| 49 | foreach ($routeCollection as $name => $route) { |
||
| 50 | if (null === ($matchResult = $route->match($request, $pathOffset))) { |
||
| 51 | continue; |
||
| 52 | } |
||
| 53 | |||
| 54 | if ($matchResult->isSuccess()) { |
||
| 55 | return MatchResult::fromChildMatch($matchResult, $parentParams, $name); |
||
| 56 | } |
||
| 57 | |||
| 58 | if ($matchResult->isMethodFailure()) { |
||
| 59 | if (null === $methodFailureResult) { |
||
| 60 | $methodFailureResult = $matchResult; |
||
| 61 | } else { |
||
| 62 | $methodFailureResult = MatchResult::mergeMethodFailures($methodFailureResult, $matchResult); |
||
| 63 | } |
||
| 64 | continue; |
||
| 65 | } |
||
| 66 | |||
| 67 | if ($matchResult->isSchemeFailure()) { |
||
| 68 | $schemeFailureResult = $schemeFailureResult ?: $matchResult; |
||
| 69 | continue; |
||
| 70 | } |
||
| 71 | |||
| 72 | return $matchResult; |
||
| 73 | } |
||
| 74 | |||
| 75 | if (null !== $schemeFailureResult) { |
||
| 76 | return $schemeFailureResult; |
||
| 77 | } |
||
| 78 | |||
| 79 | if (null !== $methodFailureResult) { |
||
| 80 | return $methodFailureResult; |
||
| 81 | } |
||
| 82 | |||
| 83 | return null; |
||
| 84 | } |
||
| 85 | } |
||
| 86 |
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.