-
Notifications
You must be signed in to change notification settings - Fork 530
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
Fix type resolution by recursing prototypes #1334
Fix type resolution by recursing prototypes #1334
Conversation
I just realized that the fixed test is broken with Done: ✅ |
77e70e2
to
60290b0
Compare
Huh I'm surprised the CI isn't running on this. Will review |
Did the main branch change from |
This fixes an issue when you have types declared in a Prototype (such as input_object input types for a directive). Previously type resolution would look on the Schema, but not the Prototype for the type definitions. You _could_ workaround this by duplicating your type definition into both the Schema and the Prototype. This makes me somewhat curious if there is a better way to fix this, in that the code that was trying to resolve the type here shouldn't be resolving it on the Schema, but rather on the Prototype 🤷. This seems to work though. Fixes absinthe-graphql#1279
1f8122e
to
fad950d
Compare
I rebased this off the latest |
Thanks! |
This fixes an issue when you have types declared in a Prototype (such as input_object input types for a directive). Previously type resolution would look on the Schema, but not the Prototype for the type definitions.
You could workaround this by duplicating your type definition into both the Schema and the Prototype. This makes me somewhat curious if there is a better way to fix this, in that the code that was trying to resolve the type here shouldn't be resolving it on the Schema, but rather on the Prototype 🤷. This seems to work though.
Fixes #1279
Also should fix the issue mentioned here: DivvyPayHQ/absinthe_federation#81