Re: [whatwg/url] Proposal of .toString({ concise: true }) for nicer output with empty values (#469)

> I think if you're trying to encode non-string JS values (in your case it sounds like string-or-null-or-undefined) ...

Given that `undefined`'s a relatively language-specific concept (in JavaScript and derived languages), whereas `null`-like values are present in most languages, I'm currently only suggesting null-or-string.

> ... you're going to need explicit buy-in from both the consumer and producer side to understand your serialization format.

That's a good argument in favour of making the change optional.  Essentially, if an application environment wants/needs to serialize the empty string and null as distinct values, then they could opt-in by setting `concise:true` (aka. `standaloneKeys:true` in the pull requests referenced).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/469#issuecomment-627188130

Received on Tuesday, 12 May 2020 08:16:48 UTC