Passed
Push — master ( b2f528...fcecd3 )
by Vítězslav
21:42
created

FlexiBeeRO::error500Reporter()   C

Complexity

Conditions 14
Paths 25

Size

Total Lines 61
Code Lines 45

Duplication

Lines 0
Ratio 0 %

Importance

Changes 2
Bugs 0 Features 0
Metric Value
eloc 45
c 2
b 0
f 0
dl 0
loc 61
rs 6.2666
cc 14
nc 25
nop 1

How to fix   Long Method    Complexity   

Long Method

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:

1
<?php
2
3
/**
4
 * FlexiPeeHP - Fake RO for backward compatibility
5
 *
6
 * @author     Vítězslav Dvořák <[email protected]>
7
 * @copyright  (C) 2015-2020 Spoje.Net
8
 */
9
10
namespace FlexiPeeHP;
11
12
/**
13
 * Please use new name \FlexiPeeHP\RO
14
 *
15
 * @deprecated since version 2.0
16
 * 
17
 * @author vitex
18
 */
19
class FlexiBeeRO extends RO {
20
    
21
}
22