GitHub Access Token became invalid

It seems like the GitHub access token used for retrieving details about this repository from GitHub became invalid. This might prevent certain types of inspections from being run (in particular, everything related to pull requests).
Please ask an admin of your repository to re-new the access token on this website.
Completed
Push — master ( 17e380...c87318 )
by Bruno
06:52
created

tests/Controller/App/AppKernel.php (1 issue)

Severity

Upgrade to new PHP Analysis Engine

These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more

1
<?php
2
3
use Symfony\Component\HttpKernel\Kernel;
4
use Symfony\Component\Config\Loader\LoaderInterface;
5
6
class AppKernel extends Kernel
7
{
8
    public function registerBundles()
9
    {
10
        $bundles = array(
11
            // Dependencies
12
            new Symfony\Bundle\FrameworkBundle\FrameworkBundle(),
13
            new Symfony\Bundle\SecurityBundle\SecurityBundle(),
14
            new Symfony\Bundle\MonologBundle\MonologBundle(),
15
            new Symfony\Bundle\TwigBundle\TwigBundle(),
16
            new Sensio\Bundle\FrameworkExtraBundle\SensioFrameworkExtraBundle(),
17
            new Doctrine\Bundle\DoctrineBundle\DoctrineBundle(),
18
19
            // My Bundle to test
20
            new Onurb\Bundle\YumlBundle\OnurbYumlBundle(),
21
        );
22
23
        return $bundles;
0 ignored issues
show
The expression return $bundles; seems to be an array, but some of its elements' types (Symfony\Bundle\MonologBu...sioFrameworkExtraBundle) are incompatible with the return type declared by the interface Symfony\Component\HttpKe...erface::registerBundles of type Symfony\Component\HttpKe...undle\BundleInterface[].

If you return a value from a function or method, it should be a sub-type of the type that is given by the parent type f.e. an interface, or abstract method. This is more formally defined by the Lizkov substitution principle, and guarantees that classes that depend on the parent type can use any instance of a child type interchangably. This principle also belongs to the SOLID principles for object oriented design.

Let’s take a look at an example:

class Author {
    private $name;

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

    public function getName() {
        return $this->name;
    }
}

abstract class Post {
    public function getAuthor() {
        return new Author('Johannes');
    }
}

class BlogPost extends Post {
    public function getAuthor() {
        return 'Johannes';
    }
}

class ForumPost extends Post { /* ... */ }

function my_function(Post $post) {
    echo strtoupper($post->getAuthor());
}

Our function my_function expects a Post object, and outputs the author of the post. The base class Post returns a simple string and outputting a simple string will work just fine. However, the child class BlogPost which is a sub-type of Post instead decided to return an object, and is therefore violating the SOLID principles. If a BlogPost were passed to my_function, PHP would not complain, but ultimately fail when executing the strtoupper call in its body.

Loading history...
24
    }
25
26
    public function registerContainerConfiguration(LoaderInterface $loader)
27
    {
28
        // We don't need that Environment stuff, just one config
29
        $loader->load(__DIR__ . '/config.yml');
30
    }
31
}
32