-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
push to named star route with empty pathMatch fails #3106
Closed
adi-zz opened this issue
Jan 19, 2020
· 1 comment
· Fixed by WFCD/warframe-hub#411, mariazevedo88/hash-generator-js#38, tghelere/valorize-vidas#9, tghelere/DeliVuery#36 or MichaelKohler/reps-voting-analysis#20
Closed
push to named star route with empty pathMatch fails #3106
adi-zz opened this issue
Jan 19, 2020
· 1 comment
· Fixed by WFCD/warframe-hub#411, mariazevedo88/hash-generator-js#38, tghelere/valorize-vidas#9, tghelere/DeliVuery#36 or MichaelKohler/reps-voting-analysis#20
Labels
Comments
The workaround for this is using a named param with a custom regexp, which will be the preferred way in the next major version: {
name: "catchAllRoute",
path: "/anything/:pathMatch(.*)"
} |
adi-zz
added a commit
to adi-zz/vue-router
that referenced
this issue
Jan 21, 2020
This was referenced Mar 14, 2020
This was referenced Mar 24, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
3.1.3
Reproduction link
https://codesandbox.io/s/vue-template-7k3sv
Steps to reproduce
https://7k3sv.csb.app/anything/123
- which is ok.What is expected?
You should get to
https://7k3sv.csb.app/anything/
.What is actually happening?
You get to
https://7k3sv.csb.app/
.I checked a couple of vue-router issues in the past, and I noticed posva has his own particular way of assessing bugs, so I know he will say this is not a bug. But is there anyone in vue-router team willing to acknowledge this is a bug? (cc @yyx990803, @kazupon)
I used the latest vue-router available on npm (3.1.5). My current issue report says I used 3.1.3 because new-issue.vuejs.org does not let me choose 3.1.5. Guys, if you force me using new-issue.vuejs.org when reporting an issue, it would be nice to keep it up-to-date.
The text was updated successfully, but these errors were encountered: