Completed
Push — master ( a032e9...21f152 )
by Dmitry
14:20
created

FakeRequest::getWorker()   A

Complexity

Conditions 1
Paths 1

Size

Total Lines 4
Code Lines 2

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
dl 0
loc 4
rs 10
c 0
b 0
f 0
cc 1
eloc 2
nc 1
nop 0
1
<?php
2
/**
3
 * Generalization over Omnipay and Payum
4
 *
5
 * @link      https://github.com/hiqdev/php-merchant
6
 * @package   php-merchant
7
 * @license   BSD-3-Clause
8
 * @copyright Copyright (c) 2015-2017, HiQDev (http://hiqdev.com/)
9
 */
10
11
namespace hiqdev\php\merchant\bitpay;
12
13
/**
14
 * BitPay Omnipay Fake Request class
15
 *
16
 * The main purpose of this class is to prevent real purchase request
17
 * dispatching to BitPay.
18
 *
19
 * Instead, this class must be initialized with data array,
20
 * that contains `inputs` key. The inputs will be used in
21
 * [[OmnipayMerchant]] to create an appropriate response.
22
 *
23
 */
24
class FakeRequest extends \hiqdev\php\merchant\OmnipayRequest
25
{
26
    public function getWorker()
27
    {
28
        return $this;
0 ignored issues
show
Bug Best Practice introduced by
The return type of return $this; (hiqdev\php\merchant\bitpay\FakeRequest) is incompatible with the return type declared by the abstract method hiqdev\php\merchant\AbstractRequest::getWorker of type Omnipay\Common\Message\A...ayum\Core\Model\Payment.

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...
29
    }
30
}
31