-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
[superset-client] getClientErrorObject
for everyone
#6276
Conversation
dispatch(annotationQuerySuccess(annotation, err, sliceKey)); | ||
} else if (err.statusText !== 'abort') { | ||
dispatch(annotationQueryFailed(annotation, err.responseJSON, sliceKey)); | ||
dispatch(annotationQueryFailed(annotation, err, sliceKey)); |
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 verified that err.error
is pulled from err
in the annotationQueryFailed
reducer
Codecov Report
@@ Coverage Diff @@
## master #6276 +/- ##
=======================================
Coverage 77.02% 77.02%
=======================================
Files 64 64
Lines 9504 9504
=======================================
Hits 7320 7320
Misses 2184 2184 Continue to review full report at Codecov.
|
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.
Thanks for fixing this so quickly!
(cherry picked from commit 7fe8e8a) (cherry picked from commit c099382)
This fixes #6272 and probably some other error 🐛 s that haven't been reported.
I searched for all instances of
SupersetClient.xxx().catch()
and if any call attempted to pull an error message from theresponse
I wrapped it in thegetClientErrorObject
which properly parses the response.Tested most of them manually by hand by inducing an error, here's the updated error for the reported bug:
@mistercrunch @kristw @michellethomas @graceguo-supercat