prlanzarin b6a962ff73 fix: not all error boundaries should close audio/Apollo ... Currently, all error boundaries close audio and Apollo connections once an error is caught. This is not the correct behavior as not all error boundaries are critical, e.g.: the presentation crashing should _not_ break the whole client. It also deviates from how error boundaries worked in 2.7 Add a new prop to the ErrorBoundary/LocatedErrorBoundary components called isCritical that flags an error boundary instance as critical. If true, it'll close Apollo/audio. The default behavior is isCritical=false, and the only critical error boundaries are the ones located in the app's root (/client/main.tsx).		2024-09-10 19:00:47 +00:00
..
located-error-boundary	Migrate auth and settings to graphQL (#19507)	2024-03-06 14:28:18 -03:00
component.jsx	fix: not all error boundaries should close audio/Apollo	2024-09-10 19:00:47 +00:00