Issues (632)

src/Helpers/SelectionHelper.php (72 issues)

1
<?php
0 ignored issues
show
This file is missing a doc comment.
Loading history...
The PHP open tag does not have a corresponding PHP close tag
Loading history...
Filename "SelectionHelper.php" doesn't match the expected filename "selectionhelper.php"
Loading history...
2
namespace EddIriarte\Console\Helpers;
0 ignored issues
show
Missing file doc comment
Loading history...
3
4
use EddIriarte\Console\Handlers\SelectHandler;
5
use Symfony\Component\Console\Formatter\OutputFormatterStyle;
6
use Symfony\Component\Console\Helper\HelperInterface;
7
use Symfony\Component\Console\Helper\HelperSet;
8
use Symfony\Component\Console\Input\InputInterface;
9
use Symfony\Component\Console\Output\OutputInterface;
10
use EddIriarte\Console\Inputs\Interfaces\SelectInput;
11
12
/**
13
 * Class SelectionHelper
14
 *
15
 * Its used for registration to symfonys output helpers.
16
 *
17
 * @package EddIriarte\Console\Helpers
0 ignored issues
show
Coding Style Documentation introduced by
@package tag is not allowed in class comment
Loading history...
18
 * @author Eduardo Iriarte <eddiriarte[at]gmail[dot]com>
0 ignored issues
show
Coding Style Documentation introduced by
@author tag is not allowed in class comment
Loading history...
Content of the @author tag must be in the form "Display Name <[email protected]>"
Loading history...
Tag value indented incorrectly; expected 2 spaces but found 1
Loading history...
19
 */
0 ignored issues
show
Missing @category tag in class comment
Loading history...
Missing @license tag in class comment
Loading history...
Missing @link tag in class comment
Loading history...
20
class SelectionHelper implements HelperInterface
21
{
0 ignored issues
show
Opening brace should be on the same line as the declaration for class SelectionHelper
Loading history...
22
    use StreamableInput;
23
24
    /**
0 ignored issues
show
Missing short description in doc comment
Loading history...
25
     * @var InputInterface
26
     */
27
    protected $input;
0 ignored issues
show
Protected member variable "input" must contain a leading underscore
Loading history...
28
29
    /**
0 ignored issues
show
Missing short description in doc comment
Loading history...
30
     * @var OutputInterface
31
     */
32
    protected $output;
0 ignored issues
show
Protected member variable "output" must contain a leading underscore
Loading history...
33
34
    /**
0 ignored issues
show
Missing short description in doc comment
Loading history...
35
     * @var null
36
     */
37
    protected $helperSet = null;
0 ignored issues
show
Protected member variable "helperSet" must contain a leading underscore
Loading history...
TRUE, FALSE and NULL should be uppercase as per the configured coding-style; instead of null please use NULL.
Loading history...
38
39
    /**
40
     * SelectionHelper constructor.
41
     * @param InputInterface $input
0 ignored issues
show
There must be exactly one blank line before the tags in a doc comment
Loading history...
Missing parameter comment
Loading history...
Expected 2 spaces after parameter type; 1 found
Loading history...
42
     * @param OutputInterface $output
0 ignored issues
show
Missing parameter comment
Loading history...
43
     */
44 5
    public function __construct(InputInterface $input, OutputInterface $output)
0 ignored issues
show
Expected 2 blank lines before function; 1 found
Loading history...
45
    {
0 ignored issues
show
Opening brace should be on the same line as the declaration
Loading history...
46 5
        $this->input = $input;
0 ignored issues
show
Equals sign not aligned with surrounding assignments; expected 2 spaces but found 1 space

This check looks for multiple assignments in successive lines of code. It will report an issue if the operators are not in a straight line.

To visualize

$a = "a";
$ab = "ab";
$abc = "abc";

will produce issues in the first and second line, while this second example

$a   = "a";
$ab  = "ab";
$abc = "abc";

will produce no issues.

Loading history...
47 5
        $this->output = $output;
48
49 5
        $this->checkAnsiSupport();
50 5
        $this->setOutputStyles();
51 5
    }
0 ignored issues
show
Expected 2 blank lines after function; 1 found
Loading history...
Expected 1 blank line before closing function brace; 0 found
Loading history...
Expected //end __construct()
Loading history...
52
53
    /**
0 ignored issues
show
Parameter $helperSet should have a doc-comment as per coding-style.
Loading history...
54
     * {@inheritdoc}
55
     */
0 ignored issues
show
Missing @return tag in function comment
Loading history...
56 2
    public function setHelperSet(HelperSet $helperSet = null)
0 ignored issues
show
TRUE, FALSE and NULL should be uppercase as per the configured coding-style; instead of null please use NULL.
Loading history...
57
    {
0 ignored issues
show
Opening brace should be on the same line as the declaration
Loading history...
58 2
        $this->helperSet = $helperSet;
0 ignored issues
show
Documentation Bug introduced by
It seems like $helperSet can also be of type Symfony\Component\Console\Helper\HelperSet. However, the property $helperSet is declared as type null. Maybe add an additional type check?

Our type inference engine has found a suspicous assignment of a value to a property. This check raises an issue when a value that can be of a mixed type is assigned to a property that is type hinted more strictly.

For example, imagine you have a variable $accountId that can either hold an Id object or false (if there is no account id yet). Your code now assigns that value to the id property of an instance of the Account class. This class holds a proper account, so the id value must no longer be false.

Either this assignment is in error or a type check should be added for that assignment.

class Id
{
    public $id;

    public function __construct($id)
    {
        $this->id = $id;
    }

}

class Account
{
    /** @var  Id $id */
    public $id;
}

$account_id = false;

if (starsAreRight()) {
    $account_id = new Id(42);
}

$account = new Account();
if ($account instanceof Id)
{
    $account->id = $account_id;
}
Loading history...
59 2
    }
0 ignored issues
show
Expected 2 blank lines after function; 1 found
Loading history...
Expected 1 blank line before closing function brace; 0 found
Loading history...
Expected //end setHelperSet()
Loading history...
60
61
    /**
62
     * {@inheritdoc}
63
     */
0 ignored issues
show
Missing @return tag in function comment
Loading history...
64 1
    public function getHelperSet()
65
    {
0 ignored issues
show
Opening brace should be on the same line as the declaration
Loading history...
66 1
        return $this->helperSet;
67
    }
0 ignored issues
show
Expected 2 blank lines after function; 1 found
Loading history...
Expected 1 blank line before closing function brace; 0 found
Loading history...
Expected //end getHelperSet()
Loading history...
68
69
    /**
70
     * {@inheritdoc}
71
     */
0 ignored issues
show
Missing @return tag in function comment
Loading history...
72 2
    public function getName()
73
    {
0 ignored issues
show
Opening brace should be on the same line as the declaration
Loading history...
74 2
        return 'selection';
75
    }
0 ignored issues
show
Expected 2 blank lines after function; 1 found
Loading history...
Expected 1 blank line before closing function brace; 0 found
Loading history...
Expected //end getName()
Loading history...
76
77
    /**
78
     * Allow multiple item selections to user.
79
     *
80
     * @param SelectInput $question
0 ignored issues
show
Missing parameter comment
Loading history...
Tag value indented incorrectly; expected 2 spaces but found 1
Loading history...
81
     * @return array
0 ignored issues
show
Tag cannot be grouped with parameter tags in a doc comment
Loading history...
82
     */
83 1
    public function select(SelectInput $question)
84
    {
0 ignored issues
show
Opening brace should be on the same line as the declaration
Loading history...
85 1
        $select = new SelectHandler($question, $this->output, $this->getInputStream());
86
87 1
        $responses = $select->handle();
88
        // TODO: validate responses  ???
0 ignored issues
show
Coding Style Best Practice introduced by
Comments for TODO tasks are often forgotten in the code; it might be better to use a dedicated issue tracker.
Loading history...
There should be no blank line after an inline comment.
Loading history...
89
90 1
        return $responses;
91
    }
0 ignored issues
show
Expected 2 blank lines after function; 1 found
Loading history...
Expected 1 blank line before closing function brace; 0 found
Loading history...
Expected //end select()
Loading history...
92
93
    /**
0 ignored issues
show
Doc comment is empty
Loading history...
94
     *
95
     */
0 ignored issues
show
Missing @return tag in function comment
Loading history...
96 5
    protected function checkAnsiSupport(): void
97
    {
0 ignored issues
show
Opening brace should be on the same line as the declaration
Loading history...
98 5
        if ($this->output->isDecorated()) {
99 3
            return;
100
        }
101
102
        // // disable overwrite when output does not support ANSI codes.
103
        // $this->overwrite = false;
0 ignored issues
show
Unused Code Comprehensibility introduced by
45% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
104
        // // set a reasonable redraw frequency so output isn't flooded
105
        // $this->setRedrawFrequency(10);
0 ignored issues
show
Unused Code Comprehensibility introduced by
72% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
106 2
    }
0 ignored issues
show
Expected 2 blank lines after function; 1 found
Loading history...
Expected 1 blank line before closing function brace; 0 found
Loading history...
Expected //end checkAnsiSupport()
Loading history...
107
108 5
    protected function setOutputStyles()
0 ignored issues
show
Missing function doc comment
Loading history...
109
    {
0 ignored issues
show
Opening brace should be on the same line as the declaration
Loading history...
110 5
        if (!$this->output->getFormatter()->hasStyle('hl')) {
0 ignored issues
show
There must be a single space after a NOT operator; 0 found
Loading history...
111 3
            $style = new OutputFormatterStyle('black', 'white');
112 3
            $this->output->getFormatter()->setStyle('hl', $style);
113
        }
114 5
    }
0 ignored issues
show
Expected 2 blank lines after function; 0 found
Loading history...
Expected 1 blank line before closing function brace; 0 found
Loading history...
Expected //end setOutputStyles()
Loading history...
115
}
0 ignored issues
show
Expected //end class
Loading history...
As per coding style, files should not end with a newline character.

This check marks files that end in a newline character, i.e. an empy line.

Loading history...
116