Perhaps follow the W3C JSON forms spec?

[ljharb]

Perhaps follow the W3C JSON forms spec?

[jonathanong]

basically, shouldn't this issue go to qs?

[dougwilson]

This is the qs repo :)

[jonathanong]

oh what. i'm blind. i thought i saw this in body-parser. :)

[jonathanong]

👍

[dougwilson]

There is one in body-parser as a tracking issue :) That issue would move forward regardless of what happens with qs, but it'd be cool if qs were the JSON forms parser :)

[nlf]

Yes! I'm so happy there's a standard that I can point to for this. Definitely going to do this, thank you for bringing this to my attention!

[dougwilson]

Cool :) The best part is it's nearly the same as this module already :) Feel free to back pedal on this issue as well; I haven't fully read the spec, and of course, you'll form better opinions on it once you do, haha.

[nlf]

Yeah, I'll read through the spec first, but I'm super excited if this will work. All the ambiguity in this module is a huge annoyance.

[dougwilson]

Plus all the bikeshedding regarding how it works :)

[nlf]

While I'd like to do this, I think this module isn't the right place for it. There are so many wild edge cases that this module already caters to that dropping them all in favor of this standard would likely cause adoption issues that I'd like to avoid. I'm going to close this for now, but potentially this could become a new module in the future.

[dougwilson]

Thanks for your thoughts, @nlf :) We'll write our own parser, then :)

[ljharb]

I'm happy to consider doing this in a semver-major bump - reopening, per expressjs/express#3039 (comment)