Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

error handling could be improved #196

Open
karenetheridge opened this issue Jan 17, 2020 · 0 comments
Open

error handling could be improved #196

karenetheridge opened this issue Jan 17, 2020 · 0 comments
Labels
usability not a bug, but this could be made better/more intuitive etc wat Causes operator confusion

Comments

@karenetheridge
Copy link
Contributor

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".

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
usability not a bug, but this could be made better/more intuitive etc wat Causes operator confusion
Projects
None yet
Development

No branches or pull requests

1 participant