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
The * rotue in HomeRoutes is necessary for PageNotFound to be rendered for a path like /home/nonExistent.
My main concern is that someone will forget to add the * route when creating a new SomethingRoutes component. Is there a good way to do a global "no match" route?
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
-
Edit: Well, I've changed my design so this question is no longer relevant to me. Maybe other people are wondering the same thing though.
So far v6 is very nice. One minor inconvenience is that I have to define a "no match" route in each
Routes
. For example:The
*
rotue inHomeRoutes
is necessary forPageNotFound
to be rendered for a path like/home/nonExistent
.My main concern is that someone will forget to add the
*
route when creating a newSomethingRoutes
component. Is there a good way to do a global "no match" route?Beta Was this translation helpful? Give feedback.
All reactions