The Graphql support part of the documentation recommends to use resolvers for custom queries and mutations.
At the same time, the beginning of the Workflow of the resolvers part recommends to see Extending API Platform documentation for more information.
The last part seems more relevant to me and more up-to-date with nowadays best pratices. I'm willing to rewrite this part using DTO, Processor and Provider to follow API Platform docs, and let the Resolver part as an alternate way to do (but not the first one). Before that, I would like to be sure if it the way to go. Can someone confirm ?
Thanks
The Graphql support part of the documentation recommends to use resolvers for custom queries and mutations.
At the same time, the beginning of the Workflow of the resolvers part recommends to see Extending API Platform documentation for more information.
The last part seems more relevant to me and more up-to-date with nowadays best pratices. I'm willing to rewrite this part using DTO, Processor and Provider to follow API Platform docs, and let the Resolver part as an alternate way to do (but not the first one). Before that, I would like to be sure if it the way to go. Can someone confirm ?
Thanks