Describe the bug
The third paragraph for the v5 suspense docs include the following when talking about throwing errors to the nearest error boundary:
If you wish to disable this, you can set the throwOnError option to false. If you wish that errors are not thrown at all, you can set the throwOnError option to false as well!
I'm guessing this is a copy/paste issue from the v4 docs, when useErrorBoundary was re-named to throwOnError
Your minimal, reproducible example
https://tanstack.com/query/v5/docs/react/guides/suspense
Steps to reproduce
- Go to https://tanstack.com/query/v5/docs/react/guides/suspense
- See the third paragraph, starts with
In addition to queries.... The last two sentences are the source of the confusion
Expected behavior
I'm guessing the second sentence can be removed, or both of them re-worked
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform
Tanstack Query adapter
None
TanStack Query version
v5
TypeScript version
No response
Additional context
No response
Describe the bug
The third paragraph for the v5 suspense docs include the following when talking about throwing errors to the nearest error boundary:
I'm guessing this is a copy/paste issue from the v4 docs, when
useErrorBoundarywas re-named tothrowOnErrorYour minimal, reproducible example
https://tanstack.com/query/v5/docs/react/guides/suspense
Steps to reproduce
In addition to queries.... The last two sentences are the source of the confusionExpected behavior
I'm guessing the second sentence can be removed, or both of them re-worked
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform
Tanstack Query adapter
None
TanStack Query version
v5
TypeScript version
No response
Additional context
No response