should `a` and `a=` be distinguished(have different value) ?

[frantic1048]

[frantic1048]

IMO: not necessary, or this could be a optional feature disabled by default.

• extra type(e.g. two different falsy values) for distinguishing a and a=(developer side)
• extra type to handle the parsing output(user side)
• any common scenario for this usage?

[whtsky]

Just curious: in what scenario would you like to treat a and a= like the same? And is there any other library supports doing this?

[frantic1048]

Node.js' querystring API could be referable.

[whtsky]

I might have missed something but I don't think Node's querystring API provided the functionality you asked

---

Oh, they do treat a as a=

[frantic1048]

Oh, they do treat a as a=

Yes, the value of Node's querystring parsed is always string.

[quininer]

As a reference, Servo's rust-url does not differentiate it.

https://play.rust-lang.org/?gist=178dbdbbbcae669fede234f726794c11&version=stable

[quininer]

https://url.spec.whatwg.org/#urlencoded-parsing

2. If bytes contains a 0x3D (=), then let name be the bytes from the start of bytes up to but excluding its first 0x3D (=), and let value be the bytes, if any, after the first 0x3D (=) up to the end of bytes. If 0x3D (=) is the first byte, then name will be the empty byte sequence. If it is the last, then value will be the empty byte sequence.
3. Otherwise, let name have the value of bytes and let value be the empty byte sequence.

According to the latest specifications, the current behavior is not correct.

[whtsky]

looks like we should support ( and make it default behaviour )