Conditions | 15 |
Paths | 144 |
Total Lines | 48 |
Code Lines | 27 |
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 |
||
26 | public function rules(): array |
||
27 | { |
||
28 | $guardian = $this->route('guardian') ?? app('cortex.auth.guardian'); |
||
29 | $guardian->updateRulesUniques(); |
||
30 | $rules = $guardian->getRules(); |
||
31 | |||
32 | $rules['password'] = $guardian->exists |
||
33 | ? 'confirmed|min:'.config('cortex.auth.password_min_chars') |
||
34 | : 'required|confirmed|min:'.config('cortex.auth.password_min_chars'); |
||
35 | |||
36 | return $rules; |
||
37 | } |
||
38 | } |
||
39 |