Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

field resolver on input types #2969

Open
Fruchtgummi opened this issue Mar 14, 2024 Discussed in #2968 · 0 comments
Open

field resolver on input types #2969

Fruchtgummi opened this issue Mar 14, 2024 Discussed in #2968 · 0 comments

Comments

@Fruchtgummi
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant