Replies: 2 comments
-
@brophdawg11 perhaps you have an idea on how to handle this? 😇 |
Beta Was this translation helpful? Give feedback.
0 replies
-
I have tried to reproduce this issue and wasn't able to do this exactly. Therefor this must be a side effect of my setup. I decided to switch to using the |
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
-
I’m using
patchRoutesOnNavigation
with 25 Module Federated Microfrontends, and while it’s been a great improvement overall, I’ve encountered an issue. When a user directly navigates to a URL or performs a hard refresh for a route not in the default route tree, a404/NoMatch
page briefly displays before being replaced by the correct, patched route. Ideally, I’d like to show my global loading indicator during this time using thestate
fromuseNavigation()
instead.Is this behavior expected with
patchRoutesOnNavigation
, or is there an alternative approach to prevent the404/NoMatch
from rendering momentarily?Beta Was this translation helpful? Give feedback.
All reactions