Replies: 4 comments
-
I'm in a similar situation where I would like to expose these errors in a toast fashion rather than crashing the interface to the route boundary. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I've added my current work around. Not great but it does work most of the time. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
EDIT: I've moved this to remix-run/react-router#10013 (comment)
Running
useFetcher().load()
that fails due to a network connection problem: eithernet::ERR_CONNECTION_REFUSED
ornet::ERR_NETWORK_CHANGED
throws an error that can't be caught an handled on the spot, it propagates up to the error boundary. The easiest way to reproduce this is to create a poll that runs theload()
in an interval, and then closing down the remix server.My work around is
I expect to be able to handle errors gracefully, but, the
load()
function is handled internally and the error cannot be caught.What are the work arounds? Is this the intention of
load()
?Beta Was this translation helpful? Give feedback.
All reactions