Implement error handling #11

New Issue

rob · 2021-12-14T19:17:12Z

rob commented

2021-12-14 19:17:12 +00:00

Error handling for pretty much everything, especially grpc-web requests

rob added the

frontend

label 2021-12-14 19:17:12 +00:00

michaelrevans commented

2022-01-01 22:59:23 +00:00

I have a proposal for this which involves useContext and useReducer in symphony to replicate the redux library - a solution that allows for application (global) level state.

This would mean creating an error handling component that is responsible for reading errors from the global state and displaying an error message (however that should be done) and manages their dismissal (automatic, or manual, or both). Each part of the application that can then produce an error simply has to add an error to the global state and respond accordingly.

Aside from this, a tool like Sentry (which has a free tier) could be good for collecting and resolving errors that are occurring unexpectedly.

I have a proposal for this which involves `useContext` and `useReducer` in symphony to replicate the `redux` library - a solution that allows for application (global) level state. This would mean creating an error handling component that is responsible for reading errors from the global state and displaying an error message (however that should be done) and manages their dismissal (automatic, or manual, or both). Each part of the application that can then produce an error simply has to add an error to the global state and respond accordingly. Aside from this, a tool like Sentry (which has a free tier) could be good for collecting and resolving errors that are occurring unexpectedly.

rob commented

2022-01-03 19:24:47 +00:00

This sounds good 👍

Error reporting via Sentry or whatever can probably be treated as a separate problem (agree it would be useful though.)

This sounds good 👍 Error reporting via Sentry or whatever can probably be treated as a separate problem (agree it would be useful though.)

Sign in to join this conversation.