-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
feat: generate resolvers for inputs if fields are missing #1404
feat: generate resolvers for inputs if fields are missing #1404
Conversation
Hi! This looks like it could use a bit of freshening up, and I think we were hoping for a test for this. |
Lol, I forgot about this PR long ago 😆 , looks like the maintainers don't really care about this feature. So I'm not sure if it's worth wasting time to refresh it. |
Hi! I'm a maintainer now, and I care! There was a period of inactivity, but we're catching up now, and this is the kind of contribution we want to prioritize. |
Cool! that's good news, in this case I will revisit it again sometime this week |
Thanks! |
@StevenACoffman @danielvladco Looks like this is broken, the generated code expects a resolver for inputs now but it fails to implement the resolver. Also, the model that was already matching using
|
I'm facing the same issue. Did you come across any workaround? |
Describe your PR and link to any relevant issues.
Generate resolvers for input type fields in case the user defined type is missing those fields.
fixes #1403
I have: