-
-
Notifications
You must be signed in to change notification settings - Fork 5k
this.$router.go without specified name or path #437
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
Comments
I doubt it works.. I'm waiting for #296 for this. |
@azamat-sharapov it works when params or query do change, which is what I'm after 😉 |
Well.. that isn't ideal in some cases, because leaves history dirty. Let's see what Evan thinks about #442 |
What I'm trying to say is that this feature request (default to current state when none specified) is orthogonal to the #296 (option to force reload the current state). Regarding the dirty history, this can already be solved with |
Closed in favor of #461 (comment) |
It would be useful to have
this.$router.go({ ... })
andv-link="{ ... }"
assume the current state to be the target ifname
orpath
are not specified, thus updating params and query string on the current state and triggeringdata
hook.This can be achieved with
this.$router.go({ name: this.$route.name, ... })
andv-link="{ name: $route.name, ... }"
, but only for named states.The text was updated successfully, but these errors were encountered: