-
Notifications
You must be signed in to change notification settings - Fork 0
Improve Error Handling #16
Copy link
Copy link
Open
Labels
bugSomething isn't workingSomething isn't workingfunctionalityRelated to site functionalityRelated to site functionalityrelease featureNeeded for production build, but not a core site featureNeeded for production build, but not a core site feature
Description
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingfunctionalityRelated to site functionalityRelated to site functionalityrelease featureNeeded for production build, but not a core site featureNeeded for production build, but not a core site feature
Type
Fields
Give feedbackNo fields configured for issues without a type.
We do a bad job error handling front-end problems, we should improve the UX behind it. Maybe some kind of "report bug" type thing?
In the codebase itself, we should also do better error-handling with promises. Currently most errors are eaten, but this should be changed to do something more intelligent.
Additionally, there should be a better, standardized way to deal with API calls that fail. This error occurs when the front-end queries the back-end, and receives a status other than 200. WebStorm at the moment has warnings for this as a reminder that this issue exists.