Closed guillemc closed 3 years ago
In a structure like this:
<Route> <!-- same as <Route path="/*"> --> <Route path="/"><h1>It is main page</h1></Route> <Route path="/books/*"> <Route path="/"><Index /></Route> <Route path="/fiction"><Page /></Route> <Route path="/drama"><Page /></Route> </Route> <Route fallback><NotFound /></Route> </Route>
Loading route "/books" also triggers the NotFound component (see the console log in this REPL).
In the site I'm developing, the NotFound is also visible briefly as a flash of content...
Is this intentional? I hoped the fallback route to only be loaded if there was no match from any previous route.
Will check it out. Thanks.
Works fine in 0.4.1.
Yep, thanks a lot!
In a structure like this:
Loading route "/books" also triggers the NotFound component (see the console log in this REPL).
In the site I'm developing, the NotFound is also visible briefly as a flash of content...
Is this intentional? I hoped the fallback route to only be loaded if there was no match from any previous route.