You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
final class PickupPointsDTO
{
/**
* @var PickupPointDTO[]
* @Serializer\Type("array<SomeNameSpace\DTO\PickupPointDTO>")
*/
private $pickupPoints;
It working without any troubles when Im executing the code.
But when I'm trying do make some tests in PHPSpec I have problem as follows:
container@09932a507bab:/var/www/project$ php bin/phpspec run tests/spec/SomeNameSpace/PickupPointsDataTransformerSpec.php
SomeNameSpace/PickupPointsDataTransformer
16 - it is transforming data to pickup point dto array
exception [exc:Doctrine\Common\Annotations\AnnotationException("[Semantical Error] The annotation "@JMS\Serializer\Annotation\Type" in property SomeNameSpace\DTO\PickupPointsDTO::$pickupPoints does not exist, or could not be auto-loaded.")] has been thrown.
50% 50% 2
1 specs
2 examples (1 passed, 1 broken)
57ms
It looks like PHPSpec is not correctly autoloading vendor classes, and in result it cannot find given annotations.
Anyone know how to force PHPSpec to read Annotations properly?
A little update, when I added a line below it started to work, so it may be sth wrong with my configuration. Any1 know what may be wrong?
function it_is_initializable()
{
AnnotationRegistry::registerLoader('class_exists');
// ...
}
The text was updated successfully, but these errors were encountered:
I have a function to transform array into object.
My DTO looks like this:
It working without any troubles when Im executing the code.
But when I'm trying do make some tests in PHPSpec I have problem as follows:
It looks like PHPSpec is not correctly autoloading vendor classes, and in result it cannot find given annotations.
Anyone know how to force PHPSpec to read Annotations properly?
A little update, when I added a line below it started to work, so it may be sth wrong with my configuration. Any1 know what may be wrong?
The text was updated successfully, but these errors were encountered: