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
Originally posted by trippel March 13, 2024
Hey everyone,
from what I understand, field resolvers are executed concurrently and therefore, I cannot expect a certain order.
Now, what I see for field resolvers in queries, it seems that sub resolvers are executed after the root resolver, so that I can pass down values via extraFields.
I tried the same approach with a field resolver on an input type. Now, in this case the execution order is reverse, so that the field resolver always gets executed before the root resolver.
Is this intended behaviour or am I totally mistaken?
Thanks for any clarification in advance.
The text was updated successfully, but these errors were encountered:
Discussed in #2968
Originally posted by trippel March 13, 2024
Hey everyone,
from what I understand, field resolvers are executed concurrently and therefore, I cannot expect a certain order.
Now, what I see for field resolvers in queries, it seems that sub resolvers are executed after the root resolver, so that I can pass down values via extraFields.
I tried the same approach with a field resolver on an input type. Now, in this case the execution order is reverse, so that the field resolver always gets executed before the root resolver.
Is this intended behaviour or am I totally mistaken?
Thanks for any clarification in advance.
The text was updated successfully, but these errors were encountered: