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
I started using ResolverMap instead of ResolverInterface, because it safes me implementing two interfaces to achieve the exact same result, even though it was added as a requirement for the new graphql type configuration.
The text was updated successfully, but these errors were encountered:
I know, probably work different, the one merges config, the other just matched against on resolve? ;) But I think nothing speaks against it working in this case the same way? :)
Example:
And the following ResolverMap:
It is also added in the graphql extension as "resolver_map".
The RESOLVE_TYPE works, but the Node.id is not invoked and the plain ID is returned.
Contrary, the resolver is correctly inherited, when defining it using the expression language:
I started using ResolverMap instead of ResolverInterface, because it safes me implementing two interfaces to achieve the exact same result, even though it was added as a requirement for the new graphql type configuration.
The text was updated successfully, but these errors were encountered: