You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea is that rather than throwing a generic error here, we return an object that contains the status information, so that the caller can then choose what to do (and perhaps throw an error if appropriate).
Based on the last few months, looks like the .code has been useful and is usually a more refined form of .status. When we don't have a .code, we throw the error with the .status and .statusText in the message, which has been sufficient. I think we may not need to do anything else here, so do you suppose we should close this out, and open a fresh issue when we have a specific need?
See #287 (comment)
The text was updated successfully, but these errors were encountered: