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
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
There is no visual difference between an api call never returning, and the api returning an unexpected error (whether that's an http 500 (api exploded) or 4xx (auth error, input validation error, data conflict etc)). Could there be more code added to the Promise.reject(..) path to differentiate between different error conditions? A modal popup indicating the error condition in on staging servers would be helpful, or a sad panda emoji otherwise, or something other than an infinite spinner which the operator interprets as "keep waiting, this is taking a long time".
The text was updated successfully, but these errors were encountered:
There is no visual difference between an api call never returning, and the api returning an unexpected error (whether that's an http 500 (api exploded) or 4xx (auth error, input validation error, data conflict etc)). Could there be more code added to the
Promise.reject(..)
path to differentiate between different error conditions? A modal popup indicating the error condition in on staging servers would be helpful, or a sad panda emoji otherwise, or something other than an infinite spinner which the operator interprets as "keep waiting, this is taking a long time".The text was updated successfully, but these errors were encountered: