We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I had some code like the following using router v0.13:
onGaugeClick(blockId) { this.transitionTo(this.getPathname(), {}, {editBlock: blockId}); },
The idea being that if I change the route to this particular component, it won't break this method.
Why were getPathname() and getQuery() removed from the State mixin in 1.0.0? Did some kind of philosophical opposition to these develop?
getPathname()
getQuery()
State
It's very convenient to be able to code up components that can modify the query in a route-agnostic way.
The text was updated successfully, but these errors were encountered:
See #1502
Sorry, something went wrong.
related to #1502, closing
No branches or pull requests
I had some code like the following using router v0.13:
The idea being that if I change the route to this particular component, it won't break this method.
Why were
getPathname()
andgetQuery()
removed from theState
mixin in 1.0.0? Did some kind of philosophical opposition to these develop?It's very convenient to be able to code up components that can modify the query in a route-agnostic way.
The text was updated successfully, but these errors were encountered: