| Conditions | 14 |
| Paths | 51 |
| Total Lines | 76 |
| Code Lines | 42 |
| Lines | 0 |
| Ratio | 0 % |
| Tests | 37 |
| CRAP Score | 14.0826 |
| Changes | 1 | ||
| 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 |
||
| 42 | 2 | $attributes = $property->getAttributes(RuleInterface::class, ReflectionAttribute::IS_INSTANCEOF); |
|
| 43 | foreach ($attributes as $attribute) { |
||
| 44 | 2 | /** @psalm-suppress UndefinedMethod */ |
|
| 45 | 2 | $rules[$property->getName()][] = $attribute->newInstance(); |
|
| 46 | 2 | } |
|
| 47 | } |
||
| 48 | |||
| 49 | return $rules; |
||
| 50 | 2 | } |
|
| 51 | } |
||
| 52 |