GetByIntegracaoIdRequest   A
last analyzed

Complexity

Total Complexity 4

Size/Duplication

Total Lines 44
Duplicated Lines 0 %

Coupling/Cohesion

Components 1
Dependencies 0

Importance

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

4 Methods

Rating   Name   Duplication   Size   Complexity  
A __construct() 0 3 1
A getIntegracaoId() 0 4 1
A setIntegracaoId() 0 5 1
A jsonSerialize() 0 6 1
1
<?php
2
3
namespace Integracao\ControlPay\Contracts\IntencaoVenda;
4
5
/**
6
 * Class GetByIntegracaoIdRequest
7
 * @package Integracao\ControlPay\Contracts\Venda
8
 */
9
class GetByIntegracaoIdRequest implements \JsonSerializable
10
{
11
    /**
12
     * @var integer
13
     */
14
    private $integracaoId;
15
16
    /**
17
     * GetByIntegracaoIdRequest constructor.
18
     */
19
    public function __construct()
20
    {
21
    }
22
23
    /**
24
     * @return int
25
     */
26
    public function getIntegracaoId()
27
    {
28
        return $this->integracaoId;
29
    }
30
31
    /**
32
     * @param int $integracaoId
33
     * @return GetByIntegracaoIdRequest
34
     */
35
    public function setIntegracaoId($integracaoId)
36
    {
37
        $this->integracaoId = $integracaoId;
38
        return $this;
39
    }
40
41
    /**
42
     * @return array
43
     */
44
    function jsonSerialize()
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
45
    {
46
        return [
47
            "integracaoId" => $this->integracaoId,
48
        ];
49
    }
50
51
52
}