Skip to content
This repository has been archived by the owner on Feb 14, 2022. It is now read-only.

Handle future errors gracefully #59

Open
stocky37 opened this issue Jan 21, 2019 · 2 comments
Open

Handle future errors gracefully #59

stocky37 opened this issue Jan 21, 2019 · 2 comments
Labels
low priority Low priority tasks tech debt Something to fix or cleanup that shouldn't effect the user experience

Comments

@stocky37
Copy link
Collaborator

If there are calculation errors or bad data from the api the app will crash completely. This is further exacerbated by the fact that current state is stored in local storage so a refresh will often not fix the issue. We need to handle this better for future unknown errors.

@stocky37 stocky37 added the enhancement New feature or request label Jan 21, 2019
@stocky37 stocky37 added this to the 1.0.0 milestone Jan 21, 2019
@stocky37 stocky37 removed this from the 1.0.0 milestone Feb 22, 2019
@stocky37 stocky37 added tech debt Something to fix or cleanup that shouldn't effect the user experience bug Something isn't working and removed enhancement New feature or request tech debt Something to fix or cleanup that shouldn't effect the user experience labels Feb 22, 2019
@stocky37
Copy link
Collaborator Author

Slightly alleviated by the fix for #47, but still a problem for any other errors that may crop up.

@stocky37 stocky37 added tech debt Something to fix or cleanup that shouldn't effect the user experience low priority Low priority tasks and removed bug Something isn't working labels Feb 22, 2019
@stocky37
Copy link
Collaborator Author

Low priority unless I start noticing problems more regularly

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
low priority Low priority tasks tech debt Something to fix or cleanup that shouldn't effect the user experience
Projects
None yet
Development

No branches or pull requests

1 participant