Skip to content
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

Improve Error Handling #16

Open
pcodes opened this issue Feb 11, 2020 · 0 comments
Open

Improve Error Handling #16

pcodes opened this issue Feb 11, 2020 · 0 comments
Labels
bug Something isn't working functionality Related to site functionality release feature Needed for production build, but not a core site feature

Comments

@pcodes
Copy link
Collaborator

pcodes commented Feb 11, 2020

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.

@pcodes pcodes added bug Something isn't working release feature Needed for production build, but not a core site feature functionality Related to site functionality labels Feb 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working functionality Related to site functionality release feature Needed for production build, but not a core site feature
Projects
None yet
Development

No branches or pull requests

1 participant