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
should decode URI #29
Comments
Rational: Typically if I do
then Riot will properly URI-encode the value (spaces, etc.). Conversely, one would expect that when doing
the outcome of selecting the link is |
@shimaore yeah, should be. Could you send a PR? |
I've been working on this. But I've found that it'll break this spec... It looks safer to keep as is, doesn't it? |
Note: to support this, change this line: var path = decodeURIComponent(getPathFromBase()) |
Closing this issue because it's related to an old router version. Please update to the latest |
The router should call
decodeURIComponent
on parameters before providing them to the callbacks, so that the callbacks receive the intended values rather than the URI-encoded values.The text was updated successfully, but these errors were encountered: