Conditions | 1 |
Paths | 1 |
Total Lines | 57 |
Code Lines | 42 |
Lines | 0 |
Ratio | 0 % |
Tests | 43 |
CRAP Score | 1 |
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 |
||
35 | 5 | public function __construct(Request $request) |
|
36 | { |
||
37 | 5 | parent::__construct($request); |
|
38 | |||
39 | 5 | $this->actions->add( |
|
40 | 5 | 'create', |
|
41 | 5 | new Action( |
|
42 | 5 | Request::METHOD_POST, |
|
43 | 5 | 'blogs.json', |
|
44 | 5 | 'blog', |
|
45 | 5 | 'blog' |
|
46 | ) |
||
47 | ); |
||
48 | 5 | $this->actions->add( |
|
49 | 5 | 'get', |
|
50 | 5 | new Action( |
|
51 | 5 | Request::METHOD_GET, |
|
52 | 5 | 'blogs/%s.json', |
|
53 | 5 | 'blog', |
|
54 | 5 | 'blog' |
|
55 | ) |
||
56 | ); |
||
57 | 5 | $this->actions->add( |
|
58 | 5 | 'all', |
|
59 | 5 | new Action( |
|
60 | 5 | Request::METHOD_GET, |
|
61 | 5 | 'blogs.json', |
|
62 | 5 | 'blogs', |
|
63 | 5 | 'blogs' |
|
64 | ) |
||
65 | ); |
||
66 | 5 | $this->actions->add( |
|
67 | 5 | 'count', |
|
68 | 5 | new Action( |
|
69 | 5 | Request::METHOD_GET, |
|
70 | 5 | 'blogs/count.json', |
|
71 | 5 | 'count', |
|
72 | 5 | 'count' |
|
73 | ) |
||
74 | ); |
||
75 | 5 | $this->actions->add( |
|
76 | 5 | 'update', |
|
77 | 5 | new Action( |
|
78 | 5 | Request::METHOD_PUT, |
|
79 | 5 | 'blogs/%s.json', |
|
80 | 5 | 'blog', |
|
81 | 5 | 'blog' |
|
82 | ) |
||
83 | ); |
||
84 | 5 | $this->actions->add( |
|
85 | 5 | 'delete', |
|
86 | 5 | new Action( |
|
87 | 5 | Request::METHOD_DELETE, |
|
88 | 5 | 'blogs/%s.json' |
|
89 | ) |
||
90 | ); |
||
91 | 5 | } |
|
92 | } |
||
93 |