-
Notifications
You must be signed in to change notification settings - Fork 64
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
Query params in named routes #63
Comments
That seems interesting considering this is thoroughly tested. Some more context would be helpful (if this is still an issue). |
The secretary readme describes a google closure history config that discards the query params from the token. This is visible if you log the navigation event. A better alternative is described here: https://gist.github.com/pleasetrythisathome/d1d9b1d74705b6771c20#file-browser-cljs-L11 |
@julienfantin I don't recall this being an issue but if it is we apologize. If you'd like to update the README and examples with something better please do. |
FWIW I just ran into this issue. query-params were coming back as nil until I used the history config in the above gist. |
Given this route definition:
and this invokation:
I'm getting:
route params nil
instead of
route params {:query-params ... }
gives the same result.
The text was updated successfully, but these errors were encountered: