-
-
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
beforeRouteEnter callbacks trigger in opposite order for nested routes #2761
Closed
posva opened this issue
May 8, 2019
· 2 comments
· Fixed by mariazevedo88/hash-generator-js#5, noprotocol/Bubblicious#3, tghelere/valorize-vidas#4, tghelere/DeliVuery#18 or tghelere/dailymages#2
Closed
beforeRouteEnter callbacks trigger in opposite order for nested routes #2761
posva opened this issue
May 8, 2019
· 2 comments
· Fixed by mariazevedo88/hash-generator-js#5, noprotocol/Bubblicious#3, tghelere/valorize-vidas#4, tghelere/DeliVuery#18 or tghelere/dailymages#2
Labels
Comments
Thanks for pointing out, I didn't check, but I didn't want to forget about this |
This was referenced Aug 29, 2019
This was referenced Sep 30, 2019
This was referenced Oct 26, 2019
This was referenced Jan 20, 2020
This was referenced Feb 5, 2020
[Snyk] Upgrade vue-router from 3.0.1 to 3.1.4
michaelwybraniec/vue-vuex-jwt-authentication-example#2
Open
This was referenced Mar 4, 2020
This was referenced Mar 24, 2020
This was referenced Apr 15, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
3.0.3
Reproduction link
https://jsfiddle.net/posva/jr8wgc4u/
Steps to reproduce
What is expected?
beforeEnter order to be the same as beforeRouteEnter, from parent to child: Foo, NestedOne, NestedTwo
What is actually happening?
The order in beforeRouteEnter is backwards
I should also check if the same happens outside of the callback
The text was updated successfully, but these errors were encountered: