Conditions | 7 |
Paths | 18 |
Total Lines | 65 |
Code Lines | 37 |
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 |
||
35 | ): void { |
||
36 | if (CToolIntro::class !== $resourceClass) { |
||
37 | return; |
||
38 | } |
||
39 | |||
40 | if (null === $user = $this->security->getUser()) { |
||
41 | throw new AccessDeniedException('Access Denied.'); |
||
42 | } |
||
43 | |||
44 | $request = $this->requestStack->getCurrentRequest(); |
||
45 | |||
46 | $courseId = $request->query->getInt('cid'); |
||
47 | $sessionId = $request->query->getInt('sid'); |
||
48 | $groupId = $request->query->getInt('gid'); |
||
49 | |||
50 | $this->addCourseLinkWithVisibilityConditions($queryBuilder, true, $courseId, $sessionId, $groupId); |
||
51 | } |
||
52 | } |
||
53 |