Searched refs:ErrorBoundary (Results 1 – 22 of 22) sorted by relevance
| /expo/docs/pages/routing/ |
| H A D | error-handling.mdx | 35 alt="Using ErrorBoundary in Expo Router to catch errors in a route component." 40 You can export a nested `ErrorBoundary` component from any route to intercept and format component-… 46 export function ErrorBoundary(props: ErrorBoundaryProps) { 58 When you export an `ErrorBoundary` the route will be wrapped with a React Error Boundary effectivel… 61 function Route({ ErrorBoundary, Component }) { 63 <Try catch={ErrorBoundary}> 70 When `ErrorBoundary` is not present, the error will be thrown to the nearest parent's `ErrorBoundar… 76 Each `ErrorBoundary` is passed the following props: 83 <APIBox header="ErrorBoundary"> 85 You can also use the default `ErrorBoundary` component for a quick UI: [all …]
|
| /expo/packages/expo-router/build/views/ |
| H A D | ErrorBoundary.d.ts.map | 1 {"version":3,"file":"ErrorBoundary.d.ts","sourceRoot":"","sources":["../../src/views/ErrorBoundary.…
|
| H A D | Try.js | 26 const { catch: ErrorBoundary, children } = this.props; 30 return react_1.default.createElement(ErrorBoundary, { error: error, retry: this.retry });
|
| H A D | ErrorBoundary.js | 6 exports.ErrorBoundary = void 0; 71 function ErrorBoundary({ error, retry }) { class 96 exports.ErrorBoundary = ErrorBoundary;
|
| H A D | ErrorBoundary.d.ts | 3 export declare function ErrorBoundary({ error, retry }: ErrorBoundaryProps): JSX.Element; function
|
| H A D | Try.js.map | 1 …ErrorBoundary` export. */\nexport type ErrorBoundaryProps = {\n /** Retry rendering the component…
|
| H A D | ErrorBoundary.js.map | 1 …ErrorBoundary.js","sourceRoot":"","sources":["../../src/views/ErrorBoundary.tsx"],"names":[],"mapp…
|
| /expo/packages/expo-router/src/views/ |
| H A D | Try.tsx | 5 /** Props passed to a page's `ErrorBoundary` export. */ 40 const { catch: ErrorBoundary, children } = this.props; 44 return <ErrorBoundary error={error} retry={this.retry} />;
|
| H A D | ErrorBoundary.tsx | 85 export function ErrorBoundary({ error, retry }: ErrorBoundaryProps) {
|
| /expo/packages/expo-router/build/ |
| H A D | exports.d.ts | 10 export { ErrorBoundary } from './views/ErrorBoundary';
|
| H A D | exports.js | 3 exports.useFocusEffect = exports.useNavigation = exports.SplashScreen = exports.ErrorBoundary = exp… 30 …"ErrorBoundary", { enumerable: true, get: function () { return ErrorBoundary_1.ErrorBoundary; } });
|
| H A D | Route.d.ts | 9 ErrorBoundary?: React.ComponentType<ErrorBoundaryProps>;
|
| H A D | useScreens.js | 65 function fromImport({ ErrorBoundary, ...component }) { field 66 if (ErrorBoundary) { 73 return react_1.default.createElement(Try_1.Try, { catch: ErrorBoundary }, children);
|
| H A D | exports.js.map | 1 …t { ErrorBoundaryProps } from './views/Try';\nexport { ErrorBoundary } from './views/ErrorBoundary…
|
| H A D | Route.js.map | 1 … = { name: string; deep: boolean };\n\nexport type LoadedRoute = {\n ErrorBoundary?: React.Compon…
|
| H A D | useScreens.js.map | 1 …ErrorBoundary, ...component }: LoadedRoute) {\n if (ErrorBoundary) {\n return {\n default…
|
| /expo/packages/expo-router/src/ |
| H A D | exports.ts | 26 export { ErrorBoundary } from './views/ErrorBoundary';
|
| H A D | Route.tsx | 10 ErrorBoundary?: React.ComponentType<ErrorBoundaryProps>;
|
| H A D | useScreens.tsx | 121 function fromImport({ ErrorBoundary, ...component }: LoadedRoute) { 122 if (ErrorBoundary) { 129 return <Try catch={ErrorBoundary}>{children}</Try>;
|
| /expo/templates/expo-template-tabs/app/ |
| H A D | _layout.tsx | 10 ErrorBoundary,
|
| /expo/docs/pages/router/reference/ |
| H A D | async-routes.mdx | 25 Loading errors are handled in the parent route, via the [`ErrorBoundary`](/routing/error-handling/#…
|
| /expo/packages/expo-router/ |
| H A D | CHANGELOG.md | 38 - Infinite renders when using ErrorBoundary in a nested layout. ([#24317](https://github.com/expo/e…
|