-
Notifications
You must be signed in to change notification settings - Fork 994
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
chore: Update graphql-server to Yoga v4 and latest subscriptions #8753
Conversation
8cc827d
to
b8452d0
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.
Looks good to me!
I pushed a change to add a resolution to the e2e tests. Without it I was getting the following error:
Setting a resolution was based on the change made in #7695 which made a similar version change for graphql-yoga
I am happy for that to be reverted if there is a better solution.
* WIP v4 yoga and gql updates * Update graphql tools bump * yarn constraints * GraphQLArmor bump * Updates scalars in studio * Updates error masking tests * Resolve yarn * yarn dedupe * Add resolution to e2e --------- Co-authored-by: Josh GM Walker <56300765+Josh-Walker-GM@users.noreply.github.com>
This PR bumps
There are some new tests for errors to ensure GraphQL errors are not masked.
Also, the behavior of the GraphQL scalar validation message has changed.
it is still an error, but now the message is masked because it is in fact a proper runtime exception (confirmed this behavior with The Guild and is how core Yoga works).
If you are in development, though the original error message about what field failed validation will be present in the extensions.
Note: I don't think this is a breaking change per se, since the scalar behavior is still an error. But, could add in release notes that the message will change.