Skip to content
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

Add path to formatError #561

Merged
merged 1 commit into from
Nov 9, 2016
Merged

Add path to formatError #561

merged 1 commit into from
Nov 9, 2016

Conversation

leebyron
Copy link
Contributor

@leebyron leebyron commented Nov 9, 2016

While path was added to the serializable error, it was not yet added to the default formatError function.

Adding this is technically breaking since it begins to expose new information from your API.

While path was added to the serializable error, it was not yet added to the default formatError function.

Adding this is technically breaking since it begins to expose new information from your API.
@leebyron leebyron merged commit 8dcc5b0 into master Nov 9, 2016
@stubailo
Copy link

stubailo commented Nov 9, 2016

How does this addition to graphql-js interact with the spec RFC?

Does that mean we're pretty comfortable with the RFC and I can start pointing people to this feature?

@leebyron leebyron deleted the format-path branch November 10, 2016 01:25
@leebyron
Copy link
Contributor Author

Yeah I like error path, I'm excited about enshrining it in spec :) - I'd say this change is mostly incremental for graphql-js since path was already a serializable field on the error object, but now it is preserved for formatError as well. This change likely should have been made a while ago.

I'd call this an experimental implementation of a near complete spec addition.

@stubailo
Copy link

Sounds good! Really excited to have this, it will make handling errors much better by default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants