Create ErrorBoundary component linked to logging

[elainen]

Would be linked to Sentry.

https://sentry.io/for/react/

[aamorozov]

Consider using https://github.com/getsentry/sentry-javascript/tree/master/packages/node

[elainen]

This may be a bigger project for our entire hz stack rather than just hz-core, since we have discussed wanting this to be part of a bigger logging configuration that we can use for new projects. See https://github.com/hzdg/dev-team/issues/9.

[aamorozov]

I think we can break it down on two things then - have a component that is responsible for reporting errors to sentry(it could be used in data fetching apis, for example) and another part will go to our cli and be responsible for automated setup of sentry for the project. What do you think?

[lettertwo]

On the component side, maybe we can build something that is sentry-agnostic and pluggable, like:

• An ErrorContextProvider that provides a report function to descendants
• An ErrorContextBoundary that consumes that report function and calls it with errors it catches

In this kind of setup, the report function might need its own spec, like:

• It takes an error and some optional context (maybe we should consult raven-js and any other popular error reporting tools for API inspo)
• It has a return protocol to indicate whether or not it reported the error (Promise<boolean>?)
• Maybe we need a compositional tool that can take two or more report functions and compose them such that:
  • They are called in order (or in parallel?)
  • They can prevent later report functions from being called? (not sure if this is useful or not)

With this kind of architecture, we could then create a SentryErrorContextProvider that provides a raven-js backed report function, but without explicitly coupling ourselves to Sentry for error reporting.

---

Questions

• Is this too much complexity for no benefit? Not sure, but seems smart to me to future-proof where we can

• What other error reporting services might we want to use? The only one i'm aware of is The Wharf App using Crashlytics

• Should this be tied into a more general 'reporting' framework that could solve other use cases like #19, or general tracking (page view, clicks, etc)?

[elainen]

Wondering if this can also be linked with the e2e thing @toastcrunch is building with cypress.

[toastcrunch]

found an example of crash reporting using cypress.io+sentry.io https://glebbahmutov.com/blog/connecting-crash-reporting-with-end-to-end-tests/