We could streamline how we show errors throughout the app as we have a few different models today.
Some views have their own error handling and can show some message on/over the current screen.
Other errors are passed up to WalletClient that shows ErrorView, but not always with full error details and not with a considered UI.
System could include:
- Rules for when errors are handled locally (non-fatal / non-blocking errors) or passed to WalletClient (blocking errors)
- Design for local error handling, which is then used throughout app
- Design for ErrorView when handling blocking errors, what should the user do next etc. (Options for restarting / resetting node, switch network, delete wallet?)
- Standardise on one Error type (MondayError vs Error vs NodeError)
We could streamline how we show errors throughout the app as we have a few different models today.
Some views have their own error handling and can show some message on/over the current screen.
Other errors are passed up to WalletClient that shows ErrorView, but not always with full error details and not with a considered UI.
System could include: