Passed
Push — feature/eco-2295/eco-2344-crea... ( 217e63...6ac028 )
by Aleksey
01:01
created

CrefoPayApiFacade::performFinishApiCall()   A

Complexity

Conditions 1
Paths 1

Size

Total Lines 2
Code Lines 0

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
eloc 0
dl 0
loc 2
rs 10
c 0
b 0
f 0
cc 1
nc 1
nop 1
1
<?php
2
3
/**
4
 * MIT License
5
 * For full license information, please view the LICENSE file that was distributed with this source code.
6
 */
7
8
namespace SprykerEco\Zed\CrefoPayApi\Business;
9
10
use Generated\Shared\Transfer\CrefoPayApiRequestTransfer;
0 ignored issues
show
Bug introduced by
The type Generated\Shared\Transfe...foPayApiRequestTransfer was not found. Maybe you did not declare it correctly or list all dependencies?

The issue could also be caused by a filter entry in the build configuration. If the path has been excluded in your configuration, e.g. excluded_paths: ["lib/*"], you can move it to the dependency path list as follows:

filter:
    dependency_paths: ["lib/*"]

For further information see https://scrutinizer-ci.com/docs/tools/php/php-scrutinizer/#list-dependency-paths

Loading history...
11
use Generated\Shared\Transfer\CrefoPayApiResponseTransfer;
0 ignored issues
show
Bug introduced by
The type Generated\Shared\Transfe...oPayApiResponseTransfer was not found. Maybe you did not declare it correctly or list all dependencies?

The issue could also be caused by a filter entry in the build configuration. If the path has been excluded in your configuration, e.g. excluded_paths: ["lib/*"], you can move it to the dependency path list as follows:

filter:
    dependency_paths: ["lib/*"]

For further information see https://scrutinizer-ci.com/docs/tools/php/php-scrutinizer/#list-dependency-paths

Loading history...
12
use Spryker\Zed\Kernel\Business\AbstractFacade;
0 ignored issues
show
Bug introduced by
The type Spryker\Zed\Kernel\Business\AbstractFacade was not found. Maybe you did not declare it correctly or list all dependencies?

The issue could also be caused by a filter entry in the build configuration. If the path has been excluded in your configuration, e.g. excluded_paths: ["lib/*"], you can move it to the dependency path list as follows:

filter:
    dependency_paths: ["lib/*"]

For further information see https://scrutinizer-ci.com/docs/tools/php/php-scrutinizer/#list-dependency-paths

Loading history...
13
14
/**
15
 * @method \SprykerEco\Zed\CrefoPayApi\Business\CrefoPayApiBusinessFactory getFactory()
16
 */
17
class CrefoPayApiFacade extends AbstractFacade implements CrefoPayApiFacadeInterface
18
{
19
    /**
20
     * {@inheritdoc}
21
     *
22
     * @api
23
     *
24
     * @param \Generated\Shared\Transfer\CrefoPayApiRequestTransfer $requestTransfer
25
     *
26
     * @return \Generated\Shared\Transfer\CrefoPayApiResponseTransfer
27
     */
28
    public function performCreateTransactionApiCall(CrefoPayApiRequestTransfer $requestTransfer): CrefoPayApiResponseTransfer
29
    {
30
        // TODO: Implement performCreateTransactionApiCall() method.
31
    }
0 ignored issues
show
Bug Best Practice introduced by
In this branch, the function will implicitly return null which is incompatible with the type-hinted return Generated\Shared\Transfe...oPayApiResponseTransfer. Consider adding a return statement or allowing null as return value.

For hinted functions/methods where all return statements with the correct type are only reachable via conditions, ?null? gets implicitly returned which may be incompatible with the hinted type. Let?s take a look at an example:

interface ReturnsInt {
    public function returnsIntHinted(): int;
}

class MyClass implements ReturnsInt {
    public function returnsIntHinted(): int
    {
        if (foo()) {
            return 123;
        }
        // here: null is implicitly returned
    }
}
Loading history...
32
33
    /**
34
     * {@inheritdoc}
35
     *
36
     * @api
37
     *
38
     * @param \Generated\Shared\Transfer\CrefoPayApiRequestTransfer $requestTransfer
39
     *
40
     * @return \Generated\Shared\Transfer\CrefoPayApiResponseTransfer
41
     */
42
    public function performReserveApiCall(CrefoPayApiRequestTransfer $requestTransfer): CrefoPayApiResponseTransfer
43
    {
44
        // TODO: Implement performReserveApiCall() method.
45
    }
0 ignored issues
show
Bug Best Practice introduced by
In this branch, the function will implicitly return null which is incompatible with the type-hinted return Generated\Shared\Transfe...oPayApiResponseTransfer. Consider adding a return statement or allowing null as return value.

For hinted functions/methods where all return statements with the correct type are only reachable via conditions, ?null? gets implicitly returned which may be incompatible with the hinted type. Let?s take a look at an example:

interface ReturnsInt {
    public function returnsIntHinted(): int;
}

class MyClass implements ReturnsInt {
    public function returnsIntHinted(): int
    {
        if (foo()) {
            return 123;
        }
        // here: null is implicitly returned
    }
}
Loading history...
46
47
    /**
48
     * {@inheritdoc}
49
     *
50
     * @api
51
     *
52
     * @param \Generated\Shared\Transfer\CrefoPayApiRequestTransfer $requestTransfer
53
     *
54
     * @return \Generated\Shared\Transfer\CrefoPayApiResponseTransfer
55
     */
56
    public function performCaptureApiCall(CrefoPayApiRequestTransfer $requestTransfer): CrefoPayApiResponseTransfer
57
    {
58
        // TODO: Implement performCaptureApiCall() method.
59
    }
0 ignored issues
show
Bug Best Practice introduced by
In this branch, the function will implicitly return null which is incompatible with the type-hinted return Generated\Shared\Transfe...oPayApiResponseTransfer. Consider adding a return statement or allowing null as return value.

For hinted functions/methods where all return statements with the correct type are only reachable via conditions, ?null? gets implicitly returned which may be incompatible with the hinted type. Let?s take a look at an example:

interface ReturnsInt {
    public function returnsIntHinted(): int;
}

class MyClass implements ReturnsInt {
    public function returnsIntHinted(): int
    {
        if (foo()) {
            return 123;
        }
        // here: null is implicitly returned
    }
}
Loading history...
60
61
    /**
62
     * {@inheritdoc}
63
     *
64
     * @api
65
     *
66
     * @param \Generated\Shared\Transfer\CrefoPayApiRequestTransfer $requestTransfer
67
     *
68
     * @return \Generated\Shared\Transfer\CrefoPayApiResponseTransfer
69
     */
70
    public function performCancelApiCall(CrefoPayApiRequestTransfer $requestTransfer): CrefoPayApiResponseTransfer
71
    {
72
        // TODO: Implement performCancelApiCall() method.
73
    }
0 ignored issues
show
Bug Best Practice introduced by
In this branch, the function will implicitly return null which is incompatible with the type-hinted return Generated\Shared\Transfe...oPayApiResponseTransfer. Consider adding a return statement or allowing null as return value.

For hinted functions/methods where all return statements with the correct type are only reachable via conditions, ?null? gets implicitly returned which may be incompatible with the hinted type. Let?s take a look at an example:

interface ReturnsInt {
    public function returnsIntHinted(): int;
}

class MyClass implements ReturnsInt {
    public function returnsIntHinted(): int
    {
        if (foo()) {
            return 123;
        }
        // here: null is implicitly returned
    }
}
Loading history...
74
75
    /**
76
     * {@inheritdoc}
77
     *
78
     * @api
79
     *
80
     * @param \Generated\Shared\Transfer\CrefoPayApiRequestTransfer $requestTransfer
81
     *
82
     * @return \Generated\Shared\Transfer\CrefoPayApiResponseTransfer
83
     */
84
    public function performRefundApiCall(CrefoPayApiRequestTransfer $requestTransfer): CrefoPayApiResponseTransfer
85
    {
86
        // TODO: Implement performRefundApiCall() method.
87
    }
0 ignored issues
show
Bug Best Practice introduced by
In this branch, the function will implicitly return null which is incompatible with the type-hinted return Generated\Shared\Transfe...oPayApiResponseTransfer. Consider adding a return statement or allowing null as return value.

For hinted functions/methods where all return statements with the correct type are only reachable via conditions, ?null? gets implicitly returned which may be incompatible with the hinted type. Let?s take a look at an example:

interface ReturnsInt {
    public function returnsIntHinted(): int;
}

class MyClass implements ReturnsInt {
    public function returnsIntHinted(): int
    {
        if (foo()) {
            return 123;
        }
        // here: null is implicitly returned
    }
}
Loading history...
88
89
    /**
90
     * {@inheritdoc}
91
     *
92
     * @api
93
     *
94
     * @param \Generated\Shared\Transfer\CrefoPayApiRequestTransfer $requestTransfer
95
     *
96
     * @return \Generated\Shared\Transfer\CrefoPayApiResponseTransfer
97
     */
98
    public function performFinishApiCall(CrefoPayApiRequestTransfer $requestTransfer): CrefoPayApiResponseTransfer
99
    {
100
        // TODO: Implement performFinishApiCall() method.
101
    }
0 ignored issues
show
Bug Best Practice introduced by
In this branch, the function will implicitly return null which is incompatible with the type-hinted return Generated\Shared\Transfe...oPayApiResponseTransfer. Consider adding a return statement or allowing null as return value.

For hinted functions/methods where all return statements with the correct type are only reachable via conditions, ?null? gets implicitly returned which may be incompatible with the hinted type. Let?s take a look at an example:

interface ReturnsInt {
    public function returnsIntHinted(): int;
}

class MyClass implements ReturnsInt {
    public function returnsIntHinted(): int
    {
        if (foo()) {
            return 123;
        }
        // here: null is implicitly returned
    }
}
Loading history...
102
}
103