Custom Trait in Model throws Exception about graphql-doctrine HOT 5 CLOSED

It would seems like you are using a \Doctrine\Common\Persistence\Mapping\Driver\MappingDriverChain, as opposed to a simple \Doctrine\Common\Persistence\Mapping\Driver\AnnotationDriver. In that case you should define a default driver in that chain. So that we can use that default driver as a fallback to read trait's annotations.

Basically you want to go in that if:

Let me know if that helps

from graphql-doctrine.

It would seems like you are using a \Doctrine\Common\Persistence\Mapping\Driver\MappingDriverChain, as opposed to a simple \Doctrine\Common\Persistence\Mapping\Driver\AnnotationDriver. In that case you should define a default driver in that chain. So that we can use that default driver as a fallback to read trait's annotations.

Basically you want to go in that if:

Let me know if that helps

from graphql-doctrine.

Yes, you suggestion helped me but this is not obviously.
I thing it would be better if AnnotationDriver for Trait has taken from Model, such as Trait is subject of Model. Some projects can already have defaultDriver set to YamlDriver or XmlDriver and change this option can not be possible.

from graphql-doctrine.

I agree with you. It would be best to use the model class, instead of the trait class.

However we don't use MappingDriverChain in our projects and I won't work on that feature. But if you are interested in it, feel free to submit a PR, covered by unit tests, then I would merge it.

from graphql-doctrine.

Ok, I will try.

from graphql-doctrine.