Conditions | 8 |
Paths | 8 |
Total Lines | 85 |
Code Lines | 49 |
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 |
||
67 | 'Could not authenticate, AuthenticationException encountered: "%s"', |
||
68 | $exception->getMessage() |
||
69 | )); |
||
70 | |||
71 | throw $exception; |
||
72 | } catch (Exception $exception) { |
||
73 | $this->samlInteractionProvider->reset(); |
||
74 | |||
75 | $this->logger->error(sprintf( |
||
76 | 'Could not authenticate, Exception of type "%s" encountered: %s', |
||
77 | get_class($exception), |
||
78 | $exception->getMessage() |
||
79 | )); |
||
80 | |||
81 | throw $exception; |
||
82 | } |
||
83 | } |
||
84 | } |
||
85 |