How to customize onCatch CatchBoundary handler?

[bpinto]

It's possible to configure a custom error component per route (or a default error component) but how can I customise the onCatch function? My use case is for notifying (sending a request) to my error reporting tool whenever an error occurs.

[tannerlinsley]

You can get all errors for a route via the onError option which takes a function that receives the error. You must rethrow the error if you want TanStack Router to keep handling it!

…

On Apr 18, 2024 at 7:18 PM -0600, Bruno Pinto ***@***.***>, wrote: It's possible to configure a custom error component per route (or a default error component) but how can I customise the onCatch function? My use case is for notifying (sending a request) to my error reporting tool whenever an error occurs. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[bpinto]

Am I right that this onError is only triggered for errors during a navigation or preload event and not for an error during rendering lifecycle?

If so, would it make sense to add a defaultErrorBoundary option to router so that we could implement a custom onCatch function at the error boundary level which would then be called on any situation? During navigation or rendering lifecycle.

Update: Maybe that is not a good idea. But I'm not quite sure how to have onError called for rendering lifecycle errors.

[bpinto]

Thank you! I somehow missed this option.