NotSpecification   A
last analyzed

Complexity

Total Complexity 4

Size/Duplication

Total Lines 39
Duplicated Lines 0 %

Coupling/Cohesion

Components 1
Dependencies 2

Importance

Changes 0
Metric Value
wmc 4
lcom 1
cbo 2
dl 0
loc 39
rs 10
c 0
b 0
f 0

4 Methods

Rating   Name   Duplication   Size   Complexity  
A __construct() 0 4 1
A evaluate() 0 4 1
A specification() 0 4 1
A not() 0 4 1
1
<?php
2
3
/**
4
 * This file is part of the Cubiche package.
5
 *
6
 * Copyright (c) Cubiche
7
 *
8
 * For the full copyright and license information, please view the LICENSE
9
 * file that was distributed with this source code.
10
 */
11
namespace Cubiche\Core\Specification;
12
13
/**
14
 * Not Specification Class.
15
 *
16
 * @author Karel Osorio Ramírez <[email protected]>
17
 */
18
class NotSpecification extends Specification
19
{
20
    /**
21
     * @var SpecificationInterface
22
     */
23
    protected $specification;
24
25
    /**
26
     * @param SpecificationInterface $specification
27
     */
28
    public function __construct(SpecificationInterface $specification)
29
    {
30
        $this->specification = $specification;
31
    }
32
33
    /**
34
     * {@inheritdoc}
35
     */
36
    public function evaluate($value)
37
    {
38
        return !$this->specification()->evaluate($value);
39
    }
40
41
    /**
42
     * @return \Cubiche\Core\Specification\SpecificationInterface
43
     */
44
    public function specification()
45
    {
46
        return $this->specification;
47
    }
48
49
    /**
50
     * {@inheritdoc}
51
     */
52
    public function not()
53
    {
54
        return $this->specification();
0 ignored issues
show
Bug Best Practice introduced by
The return type of return $this->specification(); (Cubiche\Core\Specification\SpecificationInterface) is incompatible with the return type declared by the interface Cubiche\Core\Specificati...ificationInterface::not of type Cubiche\Domain\Specifica...\SpecificationInterface.

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...
55
    }
56
}
57