Path as regex instead of strings

[Dadibom]

Vue.js / vue-router versions

2.1.10 / 2.2.1

Trying to add a route with a negative lookahead regex, path: '/(?!PathThatShouldNotBeMatched)', however the exclamation mark is automagically escaped before passed to the regex tester.

[posva]

Paths are not regexes, they're transformed to regexes.
We could maybe allow the user to use his own regexes.
Why would you need to use a custom regex in a path?

[Dadibom]

I don't really need to use custom regex, though it would make the path system more flexible. I just want a way to match everything BUT something specific. This is an alternate solution to my problem caused by #1176 , meaning that my wildcard route could have exceptions for the routes i add dynamically.

[Dadibom]

Or maybe, replace the wildcard route with something that always matches anything unmatched, that is always checked last

[Dadibom]

Like routes: [{...}], notFound: {...}

[fnlctrl]

Since the current route matching is completely done by path-to-regexp, it's very unlikely to add such feature in vue-router. @Dadibom can you check out path-to-regexp's docs and see if it's features can work for your use case?

[posva]

I should have referenced this when I saw it 😄 pillarjs/path-to-regexp#99

Anyway, I don't think we need to add anything. We should look at #1176 instead

[LinusBorg]

So can we agree to close this because we are committed to path2regexp?

@posva @fnlctrl @Dadibom

[posva]

Yes, we should close this because the real issue is #1176
Thanks for the reminder 🙂