Conditions | 1 |
Paths | 1 |
Total Lines | 53 |
Code Lines | 28 |
Lines | 0 |
Ratio | 0 % |
Changes | 1 | ||
Bugs | 0 | Features | 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 |
||
39 | public function rules() |
||
40 | { |
||
41 | return [ |
||
42 | [ |
||
43 | [ |
||
44 | 'categories_id', |
||
45 | 'language_id', |
||
46 | ], |
||
47 | 'required', |
||
48 | ], |
||
49 | [ |
||
50 | [ |
||
51 | 'categories_id', |
||
52 | 'language_id', |
||
53 | ], |
||
54 | 'integer', |
||
55 | ], |
||
56 | [ |
||
57 | [ |
||
58 | 'description', |
||
59 | 'content', |
||
60 | ], |
||
61 | 'string', |
||
62 | ], |
||
63 | [ |
||
64 | [ |
||
65 | 'created_at', |
||
66 | 'updated_at', |
||
67 | ], |
||
68 | 'safe', |
||
69 | ], |
||
70 | [ |
||
71 | [ |
||
72 | 'title', |
||
73 | 'metaKeys', |
||
74 | 'metaDescription', |
||
75 | ], |
||
76 | 'string', |
||
77 | 'max' => 255, |
||
78 | ], |
||
79 | [ |
||
80 | ['categories_id'], |
||
81 | 'exist', |
||
82 | 'skipOnError' => true, |
||
83 | 'targetClass' => Category::class, |
||
84 | 'targetAttribute' => ['categories_id' => 'id'], |
||
85 | ], |
||
86 | [ |
||
87 | ['language_id'], |
||
88 | 'exist', |
||
89 | 'skipOnError' => true, |
||
90 | 'targetClass' => Language::class, |
||
91 | 'targetAttribute' => ['language_id' => 'id'], |
||
92 | ], |
||
134 |