Ref. #5424

Right now, you can achieve this using two routes, right?
I think the matcher is complex enough: if adding a 2nd route works, we'd better not implement this.
If you think we can achieve this without adding significant complexity, we'd be happy to review a PR.

You're definitely right for a few routes this can be achieved with multiple, however the use case that found me digging in to the matcher was a locale prefix.

Basically I wanted to be able to match routes with and without the locale so I could properly redirect to the locale prefixed versions based on the system / current user locale. For this case the prefix is a route group around the entire web routes so duplication wasn't really the best option.

I think the changes shouldn't add too much complexity to the matcher as it should only be targetting the first segment if it's optional.

I'll put together a PR and some tests

For such use cases, I see two solutions:

• either register a listener that runs before RouterListener and extracts the locale before
• or import the routes twice, with and without a prefix.
  That should do the job in a few lines for a bunch of routes.

No worries, I can look at setting up a listener prior to the router to force a locale prefix instead.

@jrbarnard note that if you want to give it a try, PRs are always welcome.

@nicolas-grekas Thanks, I've been meaning to but haven't had an opportunity yet, I'll put something together this week.

Closed PR