Confusion about nested route matching

[korrat]

Following the book, I tried to set up simple nested routes, like this:

<Router>
    <main>
        <Routes fallback=|| "Page not found.">
            <ParentRoute path=StaticSegment("") view=HomePage>
                <Route path=ParamSegment("id") view=move || "test" />
                <Route path=StaticSegment("") view=move || view! { <p>"Select a contact"</p> } />
            </ParentRoute>
        </Routes>
    </main>
</Router>

However, with this order, I always get the test in the outlet, instead of Select a contact. If I switch the order around, so that the ParamSegment is the second route, this works as intended.

[korrat]

After a bit of debugging, it seems to come down to a trailing slash: The ParamSegment matches on the trailing slash and is thus preferred, even though there is no actual value for the parameter in the segment.

[gbj]

I believe you that the order changes the behavior — it will generally give you the first complete match. I can see why the trailing slash would cause it to prefer the param version instead. If you want to require the trailing slash, it may be the case that StaticSegment("/") will enforce that although I'm not 100% sure that's the case.

Trailing slash behavior has traditionally been tricky to make particularly consistent. Glad you found a workaround.