You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It doesn't seem to documented specifically, and it seems like a potential footgun. However, it seems that you get loaders and actions defined without affecting the URL, the loader only triggers when a sub-route matches (/blog/editors and not /blog).
Would be great if anyone could help me grasp the mental model of how this works, or give me a hint if I'm too creative.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm curious if anyone can elaborate on the use of
path="/"
in nested routes?Not as a root route, but as a nested route within nested routes like this:
It doesn't seem to documented specifically, and it seems like a potential footgun. However, it seems that you get loaders and actions defined without affecting the URL, the loader only triggers when a sub-route matches (
/blog/editors
and not/blog
).Would be great if anyone could help me grasp the mental model of how this works, or give me a hint if I'm too creative.
Discord post
Beta Was this translation helpful? Give feedback.
All reactions