pjordaan /
apie
| Total Complexity | 8 |
| Total Lines | 66 |
| Duplicated Lines | 0 % |
| Changes | 1 | ||
| Bugs | 0 | Features | 1 |
| 1 | <?php |
||
| 13 | class StoreExistingResourceEvent |
||
| 14 | { |
||
| 15 | /** |
||
| 16 | * @var ModifySingleResourceEvent |
||
| 17 | */ |
||
| 18 | private $event; |
||
| 19 | |||
| 20 | /** |
||
| 21 | * @var object|null |
||
| 22 | */ |
||
| 23 | private $resource; |
||
| 24 | |||
| 25 | /** |
||
| 26 | * @param ModifySingleResourceEvent|StoreNewResourceEvent $event |
||
| 27 | */ |
||
| 28 | public function __construct($event) |
||
| 29 | { |
||
| 30 | $this->event = $event; |
||
|
|
|||
| 31 | $this->setResource($event->getResource()); |
||
| 32 | } |
||
| 33 | |||
| 34 | /** |
||
| 35 | * @return string|null |
||
| 36 | */ |
||
| 37 | public function getId(): ?string |
||
| 38 | { |
||
| 39 | if ($this->event instanceof ModifySingleResourceEvent) { |
||
| 40 | return $this->event->getId(); |
||
| 41 | } |
||
| 42 | return null; |
||
| 43 | } |
||
| 44 | |||
| 45 | /** |
||
| 46 | * @return RequestInterface |
||
| 47 | */ |
||
| 48 | public function getRequest(): RequestInterface |
||
| 49 | { |
||
| 50 | return $this->event->getRequest(); |
||
| 51 | } |
||
| 52 | |||
| 53 | /** |
||
| 54 | * @return ModifySingleResourceEvent|StoreNewResourceEvent |
||
| 55 | */ |
||
| 56 | public function getEvent() |
||
| 59 | } |
||
| 60 | |||
| 61 | /** |
||
| 62 | * @return object|null |
||
| 63 | */ |
||
| 64 | public function getResource(): ?object |
||
| 65 | { |
||
| 66 | return $this->resource; |
||
| 67 | } |
||
| 68 | |||
| 69 | /** |
||
| 70 | * @param object $resource |
||
| 71 | */ |
||
| 72 | public function setResource(object $resource): void |
||
| 79 | } |
||
| 80 | } |
||
| 81 |
Loading history...
Our type inference engine has found a suspicous assignment of a value to a property. This check raises an issue when a value that can be of a mixed type is assigned to a property that is type hinted more strictly.
For example, imagine you have a variable
$accountIdthat can either hold an Id object or false (if there is no account id yet). Your code now assigns that value to theidproperty of an instance of theAccountclass. This class holds a proper account, so the id value must no longer be false.Either this assignment is in error or a type check should be added for that assignment.