-
Notifications
You must be signed in to change notification settings - Fork 961
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
[meta] Breaking changes #164
Comments
Let's include all of this in a 1.14 release. I'll make a PR to switch from qs to query-string that includes a warning for people using nested objects in their queries. |
I should note that after we ship 1.14 I think we're ready to focus in on v2 so we can cut loose all these deprecation warnings. |
All of this was shipped in 1.14. I think we can close now. |
Thanks! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Wanted to open a meta issue to keep track of things we might want to break (but not before deprecating if possible):
Major
pushState(state, path, query)
andreplaceState(state, path, query)
in favor ofpush({path, query, state})
andreplace({path, query, state})
(Accept objects in push and replace #141, Deprecate pushState/replaceState, use push/replace instead #162)Minor
qs
forquery-string
as default query string handler (Use query-string instead of qs #121)useQueries
to replacelocation.search
instead of appending (workaround in Accept objects in push and replace #141)The text was updated successfully, but these errors were encountered: