Skip to content

Conversation

@masenf
Copy link
Collaborator

@masenf masenf commented Nov 21, 2024

In some cases, a routing failure can cause the failure to be cached. When the router has a cached failure, pushing such a route will never call routeChangeComplete, and thus on_load event will never be fired for that route.

Purposely clearing the error from the router allows the page to properly load on subsequent attempts without refreshing the app.

In some cases, a routing failure can cause the failure to be cached. When the
router has a cached failure, pushing such a route will never call
routeChangeComplete, and thus on_load event will never be fired for that route.

Purposely clearing the error from the router allows the page to properly load
on subsequent attempts without refreshing the app.
@linear
Copy link

linear bot commented Nov 21, 2024

@masenf masenf merged commit 81583d4 into main Nov 21, 2024
32 checks passed
@masenf masenf deleted the masenf/unbreak-nextjs-router branch November 21, 2024 18:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants