Router doesn't support dynamic parameter before dynamic segment

[arctic-hen7]

Describe the bug
Sycamore's router doesn't seem to handle the case of a route that has a dynamic parameter (e.g. <locale>) before a dynamic segment (e.g. <slug..>), producing the error mismatch between number of capture fields and variant fields.

To Reproduce
Steps to reproduce the behavior:

Add the following lines to a router (en example I was working with):

#[to("/<locale>/post/<slug..>")]
Post { locale: String, slug: Vec<String> },

Expected behavior
Sycamore should accept the route as valid rather than generating a compile-time error.

Environment

• Sycamore: v0.5.2 (within Perseus)

Additional context
Interestingly, the route /post/<slug..>/<locale> works (with the variants in a different order), so it seems that dynamic paths are supported after dynamic segments, but not before.

[lukechu10]

Found the issue. It's a parser error. Basically, the route /<param>/<segments..> is parsed as:

RoutePathAst {
    segments: [
        DynSegments(
            "param>/<segments",
        ),
    ],
}

[arctic-hen7]

Fantastic! To clarify, is it just an error in the proc macros then? Or does it affect the lower-level path matching systems?

[lukechu10]

Fantastic! To clarify, is it just an error in the proc macros then? Or does it affect the lower-level path matching systems?

It's just an issue with the proc-macro because the routes are parsed at compile-time. Should be fixed now. I'll try to release 0.6.0 tomorrow.

[arctic-hen7]

Great, everything shouldn't blow up in my face when I try my custom routing systems then! Wow, that's fantastic! I look forward to it!