node-querystring
querystring parser for node and the browser - supporting nesting (used by Express, Connect, etc)
by tjJavaScript
Commit activity
Last 12 weeks · 0 commits
Community health
2 of 6 standards met
Recent PRs & issues
This is a workaround for IE7 where strings can't be used as arrays directly. Update pull request #80
Would turn 'true' and 'false' into booleans; ints into ints; and floats into floats.
removing myself from this repo so my issues list is cleaner :D
Recent fixes
instead of just ignoring wrong encoded uri components, we should at least unescape them with the default javascript unescape function, which doesn't break on malformed encodings. this fixes issues in a messed up iso-8859-1 environment.
qs generates incorrect querystring when nested object contains null or undefined values : See that bar parameter is not nested :( I've attached failing test for this scenario.
I'm using node-querystring as part of Express.js. After updating to the latest version of Express, the request body object passed into POST requests no longer has the function. I think I've been able to narrow this down to the changes made in #58 . Was this a deliberate change? If so, can you explain the rationale behind it? Thanks!
Repository: tj/node-querystring. Description: querystring parser for node and the browser - supporting nesting (used by Express, Connect, etc) Stars: 455, Forks: 64. Primary language: JavaScript. Languages: JavaScript (98.3%), CSS (1.7%). License: MIT. Open PRs: 7, open issues: 26. Last activity: 12y ago. Community health: 42%. Top contributors: tj, buschtoens, eivindfjeldstad, cscade, bantic, aredridel, juliangruber, jackyz, aheckmann, abecciu and others.