Replies: 1 comment 1 reply
-
I don't understand the question. You need to opt-in to use loaders, otherwise you just use plain resolvers. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi! I'm trying to migrate my graphql code from Apollo to Mercurius and ran into some issues related to "automatic loader" that will not allow the resolver field for the query that'll cause n + 1 to be executed. And the only way to solve that is to have a loader for that field.
I tried making the loader for it but the way resolver was previously structured while working with Apollo made making loaders way difficult than it should've been.
I wonder is there any way or config to temporary disable this automatic loader behaviour? Or would it be possible to add one to the later updates.
No worries if it's not possible, thanks!
Beta Was this translation helpful? Give feedback.
All reactions