b6a962ff73
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). |
||
|---|---|---|
| .. | ||
| .vscode | ||
| client | ||
| imports | ||
| private/config | ||
| public | ||
| server | ||
| .eslintignore | ||
| .eslintrc.js | ||
| .gitignore | ||
| babel.config.js | ||
| deploy.sh | ||
| jsconfig.json | ||
| package-lock.json | ||
| package.json | ||
| run-dev.sh | ||
| test-html5.sh | ||
| tsconfig.json | ||
| webpack.config.js | ||