| Conditions | 10 | 
| Paths | 10 | 
| Total Lines | 20 | 
| Code Lines | 15 | 
| Lines | 0 | 
| Ratio | 0 % | 
| Tests | 0 | 
| CRAP Score | 110 | 
| 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  | 
            ||
| 17 | public function getExceptionType($sql_state, $error_code, $error_message)  | 
            ||
| 18 |     { | 
            ||
| 19 |         switch ($error_code) { | 
            ||
| 20 | case '1216':  | 
            ||
| 21 | case '1217':  | 
            ||
| 22 | case '1451':  | 
            ||
| 23 | case '1452':  | 
            ||
| 24 | case '1701':  | 
            ||
| 25 | return ForeignKeyException::class;  | 
            ||
| 26 | |||
| 27 | case '1062':  | 
            ||
| 28 | case '1557':  | 
            ||
| 29 | case '1569':  | 
            ||
| 30 | case '1586':  | 
            ||
| 31 | return UniqueConstraintException::class;  | 
            ||
| 32 | |||
| 33 | default:  | 
            ||
| 34 | return SQLException::class;  | 
            ||
| 35 | }  | 
            ||
| 36 | }  | 
            ||
| 37 | }  | 
            ||
| 38 |