1 | <?php |
||
2 | |||
3 | declare(strict_types=1); |
||
4 | |||
5 | namespace JMS\Serializer\Construction; |
||
6 | |||
7 | use JMS\Serializer\DeserializationContext; |
||
8 | use JMS\Serializer\Metadata\ClassMetadata; |
||
9 | use JMS\Serializer\Type\Type; |
||
10 | use JMS\Serializer\Visitor\DeserializationVisitorInterface; |
||
11 | |||
12 | /** |
||
13 | * Implementations of this interface construct new objects during deserialization. |
||
14 | * |
||
15 | * @author Johannes M. Schmitt <[email protected]> |
||
16 | * |
||
17 | * @phpstan-import-type TypeArray from Type |
||
18 | */ |
||
19 | interface ObjectConstructorInterface |
||
20 | { |
||
21 | /** |
||
22 | * Constructs a new object. |
||
23 | * |
||
24 | * Implementations could for example create a new object calling "new", use |
||
25 | * "unserialize" techniques, reflection, or other means. |
||
26 | * |
||
27 | * @param mixed $data |
||
28 | * @param TypeArray $type |
||
0 ignored issues
–
show
|
|||
29 | */ |
||
30 | public function construct(DeserializationVisitorInterface $visitor, ClassMetadata $metadata, $data, array $type, DeserializationContext $context): ?object; |
||
31 | } |
||
32 |
The issue could also be caused by a filter entry in the build configuration. If the path has been excluded in your configuration, e.g.
excluded_paths: ["lib/*"]
, you can move it to the dependency path list as follows:For further information see https://scrutinizer-ci.com/docs/tools/php/php-scrutinizer/#list-dependency-paths