boolean value is stringified as string

[sht5]

if you stringify an object with a boolean key\value and then parse it the boolean is parsed as a string

const qs = require('qs'); const x = {a:2,b:false}; const str = qs.stringify(x); const xAfter = qs.parse(str); console.log(JSON.stringify(xAfter)); //{a:2,b:"false"}

[ljharb]

Everything that goes over the wire is a string; I'm not sure what else it would be?

[sht5]

I was under the impression that when parsing back i would get the same object i stringified. I see now this is not supported

[ljharb]

Unfortunately, that's absolutely not a valid expectation when dealing with query strings - it's not even a valid expectation when dealing with JSON.

[carpben]

The default should be to return true as a string. But it would be nice if you can opt in to parse a true/false strings as booleans.

[ljharb]

@carpben you should be able to do that by providing a custom encoder/decoder function.

[carpben]

I tried this:

qs.parse(history.location.search, { 
   ignoreQueryPrefix: true ,
   decoder: str => (str==="false")? false : (str==="true")? true : str
 })

But this led to a bug, changing the keys for the returned object. For example, when logging the parsed object:
{activities%5B0%5D: "16"}

[ljharb]

You do actually have to still decode things. The decoder gets additional arguments that may help.