Conditions | 1 |
Total Lines | 55 |
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 |
||
93 | public function setBody(string $body): void |
||
94 | { |
||
95 | } |
||
96 | |||
97 | public function getDateSent(): ?Chronos |
||
98 | { |
||
99 | return $this->dateSent; |
||
100 | } |
||
101 | |||
102 | public function setEmail(string $email): void |
||
103 | { |
||
104 | } |
||
105 | |||
106 | public function getType(): string |
||
107 | { |
||
108 | return 'my_type'; |
||
109 | } |
||
110 | }; |
||
111 | } |
||
112 | } |
||
113 |