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

Handling errors - details/ideas #17

Open
krystian8207 opened this issue May 26, 2022 · 0 comments
Open

Handling errors - details/ideas #17

krystian8207 opened this issue May 26, 2022 · 0 comments

Comments

@krystian8207
Copy link
Member

  1. tryCatchLog for each main observer method. When error shows:
    a) we display browser alert
    b) we print the current state (erroneous one) to the console (or events logger db)
  2. Some exceptions (also extra but higher priority):
    a) when error shown during executing restore method we:
  • before starting restore we save the previous state (if the state was empty it's okay)
  1. Extra:
    a) We save state before each operation changing cohort state (steps, filters) as a queue of states
    b) When the error is shown we display modal that allows to restore previous state (selected one from history?)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant