-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Encoded '&' in view parameters does not reach 'activate' #51
Comments
This is happening because the latest version decodes a fragment before passing it to |
Also related to aurelia/path#30 |
Seems like it might be a pretty difficult thing to work around. If you go set up a gist.run or codesandbox that I could use for debugging that would help me diagnose and prescribe a solution. |
This worked until fragment decoding started happening in 1.3.2. |
Here is the gist forked from the issue template, but it does not use the latest of the aurelia-browser-history and & and + are parsed fine |
I'm hitting something similar but my character is a % sign which when decoded twice causes an internal error... Browser history is decoding it and then route recognize tries again causing a malformed error vendor-bundle-8.5.0-1558258139.js:formatted:8422 Unhandled promise rejection URIError: URI malformed |
fixed by #53 |
I'm submitting a bug report
1.3.2
Please tell us about your environment:
Operating System:
Windows 10
Node Version:
8.9.4
NPM Version:
6.9.0
JSPM OR Webpack AND Version
webpack 4.30.0
Browser:
all
Language:
all
Current behavior:
Passing
a=b%26c
as a view query results in{a: 'b', c: true}
objectExpected/desired behavior:
What is the expected behavior?
Passing
a=b%26c
as a view query results in{a: 'b&c'}
objectWhat is the motivation / use case for changing the behavior?
An encoded parameter value is expected to reach a view unchanged
The text was updated successfully, but these errors were encountered: