Problem with escaping backslashes in custom regex in params

[jottemm]

Version

5.0.3

Reproduction link

paths.esm.dev/

Steps to reproduce

1. Update your version of vue-router to 5.0.3.

2. Use a custom regex to define i.e. an id in a route as a digit
   Try example in version 5.0.3:

definePage({
  path: "/pathxyz/:id(\\d+)",
});

(In version 5.0.2 this still works.)

3. If you have a catch all page, you'll end up there.

If you use the following instead in version 5.0.3, it will work:

definePage({
  path: "/pathxyz/:id([0-9]+)",
});

But I think, that this is at least just a workaround. Or you stay at version 5.0.2 ...

What is expected?

Custom regex is working. You get the desired route and page.

What is actually happening?

Custom regex seems to fail because you fall into the catch all page. I think, the backslashes get lost.

---

I refer to this point in the Vue Router docs: https://router.vuejs.org/guide/essentials/route-matching-syntax.html#Custom-regex-in-params

[posva]

Sorry, I don't understand based on the repro. Can you provide one using this playground ? Thank you

[posva]

I just tested and it works.
If you are using the experimental router with custom resolvers, you cannot use a regexp, you need to use a custom param parser instead, but I do have plans to add support for custom regexp for params there too but not by overriding the path, it will be overridable in definePage()

[jottemm]

Try out yourself with this repo: https://github.com/jottemm/vue-router-test

In this repos configuration with vue-router 5.0.3 you'll get an error and an empty page if you try to open the path /test/1 for example. If you then downgrade vue-router strict to 5.0.2 you'll get the test page as it should.

[posva]

I see it now, thank you! I couldn't reproduce in a different case. Already on a fix

[posva]

Fixed in 71fdbf3