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...
23
{
24
$this->shouldHaveType(Subscription::class);
25
}
26
27
function it_implements_subscription_interface(): void
The method getId() does not exist on spec\BitBag\SyliusMollie...Entity\SubscriptionSpec. Since you implemented __call, consider adding a @method annotation.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
34
$this->/** @scrutinizer ignore-call */
35
getId()->shouldReturn(null);
Loading history...
35
}
36
37
function it_gets_order(OrderInterface $order): void
The method setOrder() does not exist on spec\BitBag\SyliusMollie...Entity\SubscriptionSpec. Since you implemented __call, consider adding a @method annotation.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
The method getOrder() does not exist on spec\BitBag\SyliusMollie...Entity\SubscriptionSpec. Since you implemented __call, consider adding a @method annotation.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
The method setState() does not exist on spec\BitBag\SyliusMollie...Entity\SubscriptionSpec. Since you implemented __call, consider adding a @method annotation.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
The method getState() does not exist on spec\BitBag\SyliusMollie...Entity\SubscriptionSpec. Since you implemented __call, consider adding a @method annotation.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
The method setSubscriptionId() does not exist on spec\BitBag\SyliusMollie...Entity\SubscriptionSpec. Since you implemented __call, consider adding a @method annotation.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
The method getSubscriptionId() does not exist on spec\BitBag\SyliusMollie...Entity\SubscriptionSpec. Since you implemented __call, consider adding a @method annotation.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
The method setCustomerId() does not exist on spec\BitBag\SyliusMollie...Entity\SubscriptionSpec. Since you implemented __call, consider adding a @method annotation.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
The method getCustomerId() does not exist on spec\BitBag\SyliusMollie...Entity\SubscriptionSpec. Since you implemented __call, consider adding a @method annotation.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the ignore-call annotation
BitBagCommerce /
SyliusMolliePlugin
Loading history...
Adding explicit visibility (
private,protected, orpublic) is generally recommend to communicate to other developers how, and from where this method is intended to be used.