[metal-uri] [question] Why replacing + character with a blank space? about metal-plugins

[jbalsas]

Hey @albertmourato, the comment you point out doesn't say we're doing it because of a library but because of the javascript library, which simply means the default browser behaviour.

In the test sample you attach, the url you're passing doesn't even seem to be encoded at all... so why trying to decode it?

When URL-encoding, reserved characters are replaced by their percent-based equivalent. In particular, + characters should be turned into %2B and spaces should be replaced by + symbols in the encoded string.

The wikipedia Percent encoding article has a comprehensive description of the algorithm. In Javascript Madness: Query String Parsing you can read about the rationale of the code you're seeing in metal-uri.

Based on this, I presume the code is correct and that it's likely that your usage of it might not be. Could you take a closer look at this to see if we can sort it out?

Thanks!

[albertininm]

Hi @jbalsas ,

Thank you so much for your detailed explanation.
That must be a problem on our side.
I tried locally adding a encodeURIComponent before calling the decode function.
As expected, it worked fine.

Thank you again.