Completed
Push — master ( 8d732d...a8c54b )
by Oscar
02:44
created

Router::getServices()   A

Complexity

Conditions 1
Paths 1

Size

Total Lines 23
Code Lines 16

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
dl 0
loc 23
rs 9.0856
c 0
b 0
f 0
cc 1
eloc 16
nc 1
nop 0
1
<?php
2
3
namespace Folk\Providers;
4
5
use Fol\App;
6
use Interop\Container\ServiceProvider;
7
use Aura\Router\RouterContainer;
8
9
class Router implements ServiceProvider
10
{
11
    public function getServices()
12
    {
13
        return [
0 ignored issues
show
Bug Best Practice introduced by
The return type of return array('router' =>... return $router; }); (array<string,Closure>) is incompatible with the return type declared by the interface Interop\Container\ServiceProvider::getServices of type callable[].

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 'Johannes';
    }
}

class BlogPost extends Post {
    public function getAuthor() {
        return new Author('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...
14
            'router' => function (App $app): RouterContainer {
0 ignored issues
show
Unused Code introduced by
The parameter $app is not used and could be removed.

This check looks from parameters that have been defined for a function or method, but which are not used in the method body.

Loading history...
15
                $router = new RouterContainer();
16
17
                $map = $router->getMap();
18
                $ns = 'Folk\\Controllers';
19
20
                $map->get('index', '/', "{$ns}\\Index");
21
                $map->get('search', '/{entity}', "{$ns}\\SearchEntity");
22
                $map->get('insert', '/{entity}/new', "{$ns}\\InsertEntity");
23
                $map->put('create', '/{entity}', "{$ns}\\CreateEntity");
24
                $map->put('createField', '/{entity}/{field}', "{$ns}\\CreateEntityField");
25
                $map->get('read', '/{entity}/{id}', "{$ns}\\ReadEntity");
26
                $map->post('update', '/{entity}/{id}', "{$ns}\\UpdateEntity");
27
                $map->post('updateField', '/{entity}/{id}/{field}', "{$ns}\\UpdateEntityField");
28
                $map->delete('delete', '/{entity}/{id}', "{$ns}\\DeleteEntity");
29
30
                return $router;
31
            }
32
        ];
33
    }
34
}
35