-
-
Notifications
You must be signed in to change notification settings - Fork 107
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
URL params should be decoded #107
Comments
I have noticed it myself in a couple of apps I built. I would say it was not an intentional behavior, but in the apps I built I've fixed it in the application code. At this stage, however, I wonder if a fix for this in the router would have to be considered a breaking one, so something that would require a version 3. |
Can we create a project here: https://github.com/ItalyPaleAle/svelte-spa-router/projects? |
Let's discuss #105 separately... As i mentioned in that issue, I am waiting for changes upstream (and I still think they should fix it upstream first). While both are breaking changes, the impact is stunningly different. |
@jesseskinner Thinking more about it, this makes sense. I've accepted this and will implement it for 3.0. |
Fixed in branch v3.0-wip. Will be merged to master when I'm ready to release 3.0 |
@ItalyPaleAle that's great, thanks! |
If I have a route like
#/path/:param
and my URL is#/path/My%20Param
, I would expect the param value to be "My Param" but it ends up as "My%20Param", forcing me to rundecodeURIComponent
on each value.Is this expected behaviour, or a bug in svelte-spa-router?
The text was updated successfully, but these errors were encountered: