-
Notifications
You must be signed in to change notification settings - Fork 768
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
👽 Use .formatted instead of format_error #1327
Conversation
Hey there, if someone is able to fix the test I can merge and push a release :) Some of the test failures (with the = Nones missing) are not caused by this PR, but by this fix on graphene, released in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See my comment; once tests pass I'll merge if you tag me :)
26158f1
to
7aa2d61
Compare
null default values no more trailing newlines
7aa2d61
to
dc87546
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@erikwrede thanks! ❤ |
Thank you! 🚀 |
…ix tests * 👽 Use .formatted instead of format_error * ✅ Fix test with newer graphene null default values (graphql-python/graphene@03277a5) no more trailing newlines
This stops using the deprecated format_error removed in graphql-core v3.2 graphql-python/graphql-core@09ff14f .
GraphqlError.formatted
has been a thing since at least v1.This PR tries to solve the same thing as #1326 and #1320.
Looks like there a missing newline in test output. Not sure if to update the tests or the code.