BootstrapDateRange::add()   A
last analyzed

Complexity

Conditions 1
Paths 1

Size

Total Lines 3
Code Lines 1

Duplication

Lines 0
Ratio 0 %

Importance

Changes 1
Bugs 0 Features 0
Metric Value
eloc 1
c 1
b 0
f 0
dl 0
loc 3
rs 10
cc 1
nc 1
nop 0
1
<?php
2
3
namespace kalanis\kw_table\form_nette_bootstrap\Fields;
4
5
6
use kalanis\kw_connect\core\Interfaces\IFilterFactory;
7
use kalanis\kw_table\form_nette\Fields\AField;
8
9
10
\kalanis\kw_table\form_nette_bootstrap\Controls\BootstrapDateRange::register();
11
12
13
/**
14
 * Class BootstrapDateRange
15
 * @package kalanis\kw_table\form_nette_bootstrap\Fields
16
 */
17
class BootstrapDateRange extends AField
18
{
19
    public function getFilterAction(): string
20
    {
21
        return IFilterFactory::ACTION_RANGE;
22
    }
23
24
    public function add(): void
25
    {
26
        $this->form->addBootstrapDateRange($this->alias, null, null, $this->attributes);
0 ignored issues
show
Unused Code introduced by
The call to kalanis\kw_table\form_ne...addBootstrapDateRange() has too many arguments starting with null. ( Ignorable by Annotation )

If this is a false-positive, you can also ignore this issue in your code via the ignore-call  annotation

26
        $this->form->/** @scrutinizer ignore-call */ 
27
                     addBootstrapDateRange($this->alias, null, null, $this->attributes);

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress. Please note the @ignore annotation hint above.

Loading history...
27
    }
28
}
29