SatsAllDay 64a16373c5
Fix client-side error boundary (#623)
* * add error boundary immediately above page component

* send error logs to server via LoggerContext

* display error stack and component stack in copyable text area

* wrap every context provider in an error boundary

* memoize context values to fix error boundary propagation issue

* Wrap page component in an error boundary so we can use our context utilities
for a better experience, like toast and logger

Still have a top-level error boundary that catches things from the context providers,
just in case.

Don't display the whole error stack, just because it's ugly, but make it copyable
2023-11-19 14:24:56 -06:00
..
2023-11-19 14:16:35 -06:00
2023-11-12 10:46:06 -06:00
2023-11-10 18:18:10 -06:00
2023-11-10 18:18:10 -06:00
2023-11-19 14:24:56 -06:00
2023-09-23 20:19:35 -05:00
2023-07-24 13:53:53 -05:00
2023-11-08 18:17:01 -06:00
2023-11-12 11:59:18 -06:00
2023-07-24 13:53:53 -05:00