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

apollo-engine-reporting: don't fail if errors have non-array 'path' #3112

Merged
merged 2 commits into from
Jul 31, 2019

Conversation

glasser
Copy link
Member

@glasser glasser commented Jul 31, 2019

Specifically, we found that some network errors talking to federated backends
could have a string path.

@glasser glasser requested a review from abernix July 31, 2019 00:40
Specifically, we found that some network errors talking to federated backends
could have a string path.
@glasser
Copy link
Member Author

glasser commented Jul 31, 2019

Feel free to merge and release.

@abernix abernix merged commit 1acf62d into master Jul 31, 2019
@abernix abernix deleted the glasser/aer-path-array branch July 31, 2019 10:48
@abernix abernix added this to the Release 2.8.x milestone Jul 31, 2019
abernix pushed a commit to apollographql/federation that referenced this pull request Sep 4, 2020
…pollographql/apollo-server#3112)

* apollo-engine-reporting: don't fail if errors have non-array 'path'

Specifically, we found that some network errors talking to federated backends
could have a string path.

* Just use `Array.isArray`, which returns `false` when passed `undefined`.

Nit, of course.

Apollo-Orig-Commit-AS: apollographql/apollo-server@1acf62d
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants