-
Notifications
You must be signed in to change notification settings - Fork 2k
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
apollo-server-core: use UserInputError for variable coercion errors #5091
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -134,7 +134,9 @@ export function toApolloError( | |
|
||
export interface ErrorOptions { | ||
code?: string; | ||
errorClass?: typeof ApolloError; | ||
// This declaration means it takes any "class" that has a constructor that | ||
// takes a single string, and should be invoked via the `new` operator. | ||
errorClass?: new (message: string) => ApolloError; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This seems fine, maybe a comment here that explains, though I also think it's pretty self-explanatory if you look at it for a second. FWIW, I tried to improve the type here a bit with no luck - I tried to make this "condition" into an interface that There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Added a comment. FWIW I find this type to be easier to understand than |
||
} | ||
|
||
export function fromGraphQLError(error: GraphQLError, options?: ErrorOptions) { | ||
|
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.
I don't know why codecov thinks this is uncovered. There's a test!