add optional separator support to stringify

[tetsuo]

stringify({foo:1,bar:2}, null, ';'); // foo=1;bar=2

[rlidwka]

I think that "null" really calls for an option object...

[tetsuo]

That's right. Changed stringify to accept an object now, keeping backwards compatibility:

stringify({foo:1,bar:2}, {separator: ';'}); // it is options if object is given
stringify({foo:1,bar:2}, 'foo'); // it is prefix if string is given
stringify({foo:1,bar:2}, {separator: ';', prefix: 'foo'}); // ...

[tj]

why not just use & like everyone else on the planet :D

[tetsuo]

heh, well semicolons is the new sexy. Resistance is futile.

[jonathanong]

kind of tempted to go full mongodb-retard with querystrings and ;.

?a.b.c=1;key5.0=null;something=else;

and use something like https://github.com/hughsk/flat. heh

[rlidwka]

heh, well semicolons is the new sexy

Yeah, I know quite a few people who have been saving semicolons in their js source code hoping to insert them into query strings instead. :P

[tetsuo]

actually it is quite possible that there are more people who use semicolons in query strings than people who use them correctly in sentences.