You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Defaults to the global query config's `useErrorBoundary` value, which is `undefined`
71
+
- Set this to `true` if you want mutation errors to be thrown in the render phase and propagate to the nearest error boundary
72
+
- Set this to `false` to disable the behaviour of throwing errors to the error boundary.
73
+
- If set to a function, it will be passed the error and should return a boolean indicating whether to show the error in an error boundary (`true`) or return the error as state (`false`)
- Defaults to the global query config's `useErrorBoundary` value, which is `undefined`
175
+
- Set this to `true` if you want errors to be thrown in the render phase and propagate to the nearest error boundary
176
+
- Set this to `false` to disable `suspense`'s default behaviour of throwing errors to the error boundary.
177
+
- If set to a function, it will be passed the error and should return a boolean indicating whether to show the error in an error boundary (`true`) or return the error as state (`false`)
* Whether errors should be thrown instead of setting the `error` property.
166
+
* If set to `true` or `suspense` is `true`, all errors will be thrown to the error boundary.
167
+
* If set to `false` and `suspense` is `false`, errors are returned as state.
168
+
* If set to a function, it will be passed the error and should return a boolean indicating whether to show the error in an error boundary (`true`) or return the error as state (`false`).
0 commit comments