Problems with '+' decode

[Kompavand]

I use
encodeURIComponent(someUriPath)
It encodes '+' as '%2B' and whitespace as '%20'
When I try to use queryString.parse() with enabled decode option i see that '%20' decodes as whitespace and '%2B' decodes as whitespace too.
Is that normal behaviour?

P.S. When i use decode-uri-component library directly '%2B decodes as '+'.

[sindresorhus]

Duplicate of #119

[Kompavand]

Is it really duplicate?

I see only solution that prevents decoding with disabled decode option.

But I don't see in #119 something about how should be %2B decoded (whitespace or +).

As i said, in query-string library %2B decodes as whitespace now, however https://github.com/SamVerschueren/decode-uri-component decodes it as + and JS function decodeURIComponent() too.

If this is normal behaviour, i don't understand why and how can I get + character from URI using this library.

[sindresorhus]

Did you see the linked Stack Overflow answer: https://stackoverflow.com/questions/2678551/when-to-encode-space-to-plus-or-20/2678602#2678602 ?

[Kompavand]

Yes, I did exactly in this way. But in result i got only spaces

[Kompavand]

I'm sorry, maybe i miss something or maybe my English is too bad, but I really want to understand is that bug, or i'm doing something wrong

[Kompavand]

@sindresorhus Problem resolved by changing arrayFormat option from 'separator' to 'comma'.
Please check if it is a bug.
Also noticed that separator character always works as separator even if it's encoded. For example with , separator 11,12 parsed as array and 11%2C12 parsed as array too. So you can't use separator character in params

[sindresorhus]

// @cheqianxiao