The type EasyWeChat\Payment\LuckyMoney\LuckyMoney has been defined more than once; this definition is ignored, only the first definition in src/Payment/luckymoney/LuckyMoney.php (L28-108) is considered.
This check looks for classes that have been defined more than once.
If you can, we would recommend to use standard object-oriented programming
techniques. For example, to avoid multiple types, it might make sense to create a
common interface, and then multiple, different implementations for that interface.
This also has the side-effect of providing you with better IDE auto-completion,
static analysis and also better OPCode caching from PHP.
The type EasyWeChat\Payment\LuckyMoney\LuckyMoney has been defined more than once; this definition is ignored, only the first definition in src/Payment/luckymoney/LuckyMoney.php (L28-108) is considered.
This check looks for classes that have been defined more than once.
If you can, we would recommend to use standard object-oriented programming
techniques. For example, to avoid multiple types, it might make sense to create a
common interface, and then multiple, different implementations for that interface.
This also has the side-effect of providing you with better IDE auto-completion,
static analysis and also better OPCode caching from PHP.
This class seems to be duplicated in your project.
Duplicated code is one of the most pungent code smells. If you need to duplicate
the same code in three or more different places, we strongly encourage you to
look into extracting the code into a single class or operation.
You can also find more detailed suggestions in the “Code” section of your repository.
This class seems to be duplicated in your project.
Duplicated code is one of the most pungent code smells. If you need to duplicate
the same code in three or more different places, we strongly encourage you to
look into extracting the code into a single class or operation.
You can also find more detailed suggestions in the “Code” section of your repository.
This class seems to be duplicated in your project.
Duplicated code is one of the most pungent code smells. If you need to duplicate
the same code in three or more different places, we strongly encourage you to
look into extracting the code into a single class or operation.
You can also find more detailed suggestions in the “Code” section of your repository.
Loading history...
29
{
30
/**
31
* @var API
32
*/
33
protected $api;
34
35
/**
36
* Merchant instance.
37
*
38
* @var \EasyWeChat\Payment\Merchant
39
*/
40
protected $merchant;
41
42
/**
43
* Constructor.
44
*
45
* @param Merchant $merchant
46
*/
47
public function __construct(Merchant $merchant)
48
{
49
$this->merchant = $merchant;
50
}
51
52
/**
53
* Merchant setter.
54
*
55
* @param Merchant $merchant
56
*/
57
public function setMerchant(Merchant $merchant)
58
{
59
$this->merchant = $merchant;
60
}
61
62
/**
63
* Merchant getter.
64
*
65
* @return Merchant
66
*/
67
public function getMerchant()
68
{
69
return $this->merchant;
70
}
71
72
/**
73
* API setter.
74
*
75
* @param API $api
76
*/
77
public function setAPI(API $api)
78
{
79
$this->api = $api;
80
}
81
82
/**
83
* Return API instance.
84
*
85
* @return API
86
*/
87
public function getAPI()
88
{
89
return $this->api ?: $this->api = new API($this->getMerchant());
overtrue /
wechat
Loading history...
This check looks for classes that have been defined more than once.
If you can, we would recommend to use standard object-oriented programming techniques. For example, to avoid multiple types, it might make sense to create a common interface, and then multiple, different implementations for that interface.
This also has the side-effect of providing you with better IDE auto-completion, static analysis and also better OPCode caching from PHP.