SherifElfadaly /
Laravel-Api-Skeleton
| Conditions | 1 |
| Paths | 1 |
| Total Lines | 133 |
| 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 namespace App\Modules\V1\Core\Utl; |
||
| 5 | public function getConfig() |
||
| 6 | { |
||
| 7 | return [ |
||
| 8 | /** |
||
| 9 | * Specify what relations should be used for every model. |
||
| 10 | */ |
||
| 11 | 'relations' => config('relations'), |
||
| 12 | /** |
||
| 13 | * Specify caching config for each api. |
||
| 14 | */ |
||
| 15 | 'cacheConfig' => config('cache_config'), |
||
| 16 | ]; |
||
| 17 | } |
||
| 18 | } |
