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
Now I would expect that the param field from the loader data is either the string I've passed (the result of whatever encodeURIComponent(JSON.stringify({ test: 'öpsdgd=$%&!%"&___...Ä+~~' })) returns OR a version of that string which has been already decoded with decodeURIComponent.
Instead I'm getting a malformed result which can't be put into the decodeURIComponent because its not a valid URI.
System Info
Shouldn't matter
Used Package Manager
npm
Expected Behavior
A predicatble behavior of the params field in the loader
Actual Behavior
The params field does some kind of transformation with the params which is unexpected.
The text was updated successfully, but these errors were encountered:
Reproduction
Example: https://stackblitz.com/edit/github-xk9p5y-9ttpl5?file=app%2Froutes%2Findex.tsx
I'm having a loader which receives one parameter called
param
. This loader is called via a fetcher like:The loader itself returns the params without making any modifications to it:
Now I would expect that the
param
field from the loader data is either the string I've passed (the result of whateverencodeURIComponent(JSON.stringify({ test: 'öpsdgd=$%&!%"&___...Ä+~~' }))
returns OR a version of that string which has been already decoded withdecodeURIComponent
.Instead I'm getting a malformed result which can't be put into the
decodeURIComponent
because its not a valid URI.System Info
Shouldn't matter
Used Package Manager
npm
Expected Behavior
A predicatble behavior of the
params
field in the loaderActual Behavior
The
params
field does some kind of transformation with the params which is unexpected.The text was updated successfully, but these errors were encountered: