Passed
Push — master ( e45b53...cf614d )
by Austin
01:43
created

Reader::generate()   F

Complexity

Conditions 18
Paths 3457

Size

Total Lines 67
Code Lines 44

Duplication

Lines 67
Ratio 100 %

Importance

Changes 0
Metric Value
cc 18
eloc 44
nc 3457
nop 1
dl 67
loc 67
rs 2.6879
c 0
b 0
f 0

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
 * src/Reader.php
4
 *
5
 * @package     php-security-txt
6
 * @author      Austin Heap <[email protected]>
7
 * @version     v0.3.0
8
 */
9
10
declare(strict_types=1);
11
12
namespace AustinHeap\Security\Txt;
13
14
/**
15
 * Reader
16
 *
17
 * @link        https://github.com/austinheap/php-security-txt
18
 * @link        https://packagist.org/packages/austinheap/php-security-txt
19
 * @link        https://austinheap.github.io/php-security-txt/classes/AustinHeap.Security.Txt.Reader.html
20
 */
21
class Reader extends SecurityTxt
22
{
23
24
    /**
25
     * Create a new Reader instance.
26
     *
27
     * @return Reader
28
     */
29
    public function __construct()
30
    {
31
        return parent::__construct($this);
32
    }
33
34
}
35