Completed
Pull Request — master (#9)
by Tomáš
06:57 queued 03:47
created

SculpinPaginationExtension   A

Complexity

Total Complexity 1

Size/Duplication

Total Lines 24
Duplicated Lines 0 %

Coupling/Cohesion

Components 0
Dependencies 2

Test Coverage

Coverage 0%

Importance

Changes 0
Metric Value
wmc 1
lcom 0
cbo 2
dl 0
loc 24
ccs 0
cts 7
cp 0
rs 10
c 0
b 0
f 0

1 Method

Rating   Name   Duplication   Size   Complexity  
A loadConfiguration() 0 7 1
1
<?php
2
3
/*
4
 * This file is a part of Sculpin.
5
 *
6
 * (c) Dragonfly Development Inc.
7
 *
8
 * For the full copyright and license information, please view the LICENSE
9
 * file that was distributed with this source code.
10
 */
11
12
namespace Symplify\PHP7_Sculpin\Bundle\PaginationBundle\DI;
13
14
use Nette\DI\Compiler;
15
use Nette\DI\CompilerExtension;
16
17
final class SculpinPaginationExtension extends CompilerExtension
18
{
19
    public function loadConfiguration()
20
    {
21
        Compiler::loadDefinitions(
22
            $this->getContainerBuilder(),
23
            $this->loadFromFile(__DIR__.'/Resources/config/services.yml')
0 ignored issues
show
Bug introduced by
It seems like $this->loadFromFile(__DI...s/config/services.yml') targeting Nette\DI\CompilerExtension::loadFromFile() can also be of type string; however, Nette\DI\Compiler::loadDefinitions() does only seem to accept array, maybe add an additional type check?

This check looks at variables that are passed out again to other methods.

If the outgoing method call has stricter type requirements than the method itself, an issue is raised.

An additional type check may prevent trouble.

Loading history...
24
        );
25
    }
26
27
    // todo: set configuration parameter alias
28
29
//    public function getConfiguration() : ConfigurationInterface
0 ignored issues
show
Unused Code Comprehensibility introduced by
47% 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...
30
//    {
31
//        return new Configuration();
32
//    }
33
34
//    protected function getParametersAliases() : array
0 ignored issues
show
Unused Code Comprehensibility introduced by
46% 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...
35
//    {
36
//        return [
37
//            'max_per_page' => 'sculpin_pagination.max_per_page',
38
//        ];
39
//    }
40
}
41