You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 25, 2022. It is now read-only.
Originally posted by raulmabe October 12, 2021
I am trying to push a route (/search) with queryParams from a top-level route (/) but throws AssertionError because of the following constraint assert(identical(match.queryParams, matches.first.queryParams)); in line 661.
Is it incompatible to use push and queryParams at the same time? Same happens with the extra property
The text was updated successfully, but these errors were encountered:
I am currently having an issue navigating to a route with a param, where the param could contain a space when navigating. So does this address that issue, or should I submit a new one?
I am currently having an issue navigating to a route with a param, where the param could contain a space when navigating. So does this address that issue, or should I submit a new one?
That sounds like a new one
I was using params instead of queryParams which doesn't allow empty spaces 😅. Also, I had the original issue submitted by @raulmabe, which I can also confirm fixed in v2.1.2.
Thanks! 🙏
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
params, queryParams and the extra param are all supported for push but not all are working at the moment. I'll fix asap.
Discussed in #88
Originally posted by raulmabe October 12, 2021
I am trying to push a route (
/search
) withqueryParams
from a top-level route (/
) but throwsAssertionError
because of the following constraintassert(identical(match.queryParams, matches.first.queryParams));
in line 661.Is it incompatible to use push and
queryParams
at the same time? Same happens with theextra
propertyThe text was updated successfully, but these errors were encountered: