Conditions | 1 |
Paths | 1 |
Total Lines | 59 |
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 |
||
46 | $this->entityManager->flush(); |
||
47 | } |
||
48 | |||
49 | public function create(ClientId $clientId, DataBag $parameters, ?UserAccountId $ownerId): ClientInterface |
||
50 | { |
||
51 | return new Client($clientId, $parameters, $ownerId); |
||
52 | } |
||
53 | |||
54 | public function createClientId(): ClientId |
||
55 | { |
||
56 | return new ClientId(\bin2hex(random_bytes(32))); |
||
57 | } |
||
58 | } |
||
59 |