Conditions | 1 |
Paths | 1 |
Total Lines | 118 |
Code Lines | 100 |
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 |
||
43 | $library = $builder->buildFromJson($json); |
||
44 | |||
45 | self::assertInstanceOf(Uuid::class, $library->getFromEventLogUuid()); |
||
46 | self::assertInstanceOf(Uuid::class, $library->getUntilEventLogUuid()); |
||
47 | |||
48 | self::assertInstanceOf(ProductCollection::class, $library->getProducts()); |
||
49 | self::assertInstanceOf(DiscountCollection::class, $library->getDiscounts()); |
||
50 | self::assertInstanceOf(ProductCollection::class, $library->getDeletedProducts()); |
||
51 | self::assertInstanceOf(DiscountCollection::class, $library->getDeletedDiscounts()); |
||
52 | } |
||
53 | } |
||
54 |