It seems like $type of type object<hiqdev\php\billing\type\TypeInterface> is incompatible with the declared type object<hiqdev\php\billing\price\Type> of property $type.
Our type inference engine has found an assignment to a property that is incompatible
with the declared type of that property.
Either this assignment is in error or the assigned type should be added
to the documentation/type hint for that property..
It seems like $target of type object<hiqdev\php\billing\target\TargetInterface> is incompatible with the declared type object<hiqdev\php\billing\price\Target> of property $target.
Our type inference engine has found an assignment to a property that is incompatible
with the declared type of that property.
Either this assignment is in error or the assigned type should be added
to the documentation/type hint for that property..
The return type of return $this->type; (hiqdev\php\billing\price\Type) is incompatible with the return type declared by the interface hiqdev\php\billing\price\PriceInterface::getType of type hiqdev\php\billing\type\TypeInterface.
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.
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.
The return type of return $this->target; (hiqdev\php\billing\price\Target) is incompatible with the return type declared by the interface hiqdev\php\billing\price\PriceInterface::getTarget of type hiqdev\php\billing\target\TargetInterface.
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.
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...
70
}
71
72
/**
73
* {@inheritdoc}
74
* Default sum calculation method: sum = price * usage.
75
*/
76
1
public function calculateSum(QuantityInterface $quantity)
77
{
78
1
$usage = $this->calculateUsage($quantity);
79
1
if ($usage === null) {
80
return null;
81
}
82
83
1
$price = $this->calculatePrice($quantity);
84
1
if ($price === null) {
85
return null;
86
}
87
88
1
return $price->multiply($usage->getQuantity());
89
}
90
91
public static function create(array $data)
92
{
93
return new SinglePrice($data['id'], $data['target']);
Our type inference engine has found an assignment to a property that is incompatible with the declared type of that property.
Either this assignment is in error or the assigned type should be added to the documentation/type hint for that property..