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
Using enums as argument default values is broken on InterfaceType #995
Comments
From traceback it seems that this is an issue with graphql-core and not with Ariadne? |
It's not clear to me which library is at fault, the exception being raised is in the exact same function of graphql-core as #547 and that particular issue was patched in ariadne, so I thought maybe that patch was missing this edge case. |
Right, it may be as simple fix as adding Interface path to our enums fixer. |
That seems to have fixed it. It's not likely for proper bugfix release because I have like 4 workhours left in this year before going for vacation, but I'll release 0.17.1 beta with the fix to let you test if my changes will solve this for you, @dkbarn |
That would be great if you could put out a beta, thanks! |
Released fix in Ariadne 0.17.1b1. I'll keep this task open and on me so I remember to do a proper release in January when I'm back in the office. |
Confirmed that 0.17.1b1 resolves the issue. Many thanks! Will look forward to a proper release in the new year. |
0.17.1 released, moving on to making announcements. |
Similar to #547 but this bug is specific to type "interface". It seems that if you try to define a schema in which an interface type contains an enum argument with a default value, an error will be thrown when trying to execute an introspection query. This is with:
ariadne 0.16.1
graphql-core 3.2.3
Example:
Error:
The text was updated successfully, but these errors were encountered: