enhance: throw located GraphQLError instead of TypeError #1764
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🚀 Website PreviewThe latest changes to the website are available as preview in: https://21afa8a5.graphql-scalars.pages.dev |
enisdenjo
approved these changes
Nov 9, 2022
Comment on lines
+14
to
+27
| export function createGraphQLError(message: string, options?: GraphQLErrorOptions): GraphQLError { | ||
| if (versionInfo.major >= 17) { | ||
| return new GraphQLError(message, options); | ||
| } | ||
| return new GraphQLError( | ||
| message, | ||
| options?.nodes, | ||
| options?.source, | ||
| options?.positions, | ||
| options?.path, | ||
| options?.originalError, | ||
| options?.extensions | ||
| ); | ||
| } |
There was a problem hiding this comment.
I avoided bundling graphql-tools by copying over the factory function.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🚨 IMPORTANT: Please do not create a Pull Request without creating an issue first.
Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of the pull request.
Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Related # (issue)
Type of change
Please delete options that are not relevant.
Screenshots/Sandbox (if appropriate/relevant):
Adding links to sandbox or providing screenshots can help us understand more about this PR and take action on it as appropriate
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Test Environment:
Checklist:
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...