-
Notifications
You must be signed in to change notification settings - Fork 0
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
Feature: reload + navigate to route #24
Comments
I think this ought to do what you want: router.go(destination, { param }) && router.reload({}, true) The URL and the current route params will change (with a call to Is that satisfactory? |
I see, that makes sense! Thanks, I'll give that a shot. |
Hmm, this has the effect of pushing the target path, with current parameter on the stack before navigating to target path with target parameter (therefore back button takes you to new synthetic location), but it's probably fine. e.g. |
Hmm that's weird. Looking at the source, there might be a bug with the reload method, but I wouldn't expect it to manifest like that. Does this work? router.go(destination, { param }) && window.location.reload() |
go
will navigate to specified routereload
will (optionally) reload and navigate to current routeIt would be handy to have support for reloading targeting a different destination, e.g.:
The text was updated successfully, but these errors were encountered: