Re: [whatwg/url] Allow encoding of null values in `application/x-www-form-urlencoded`. (Issue #732)

@domenic I'm personally fine with that model, but the reality is a fairly predominant pattern of people interpreting `x` itself as `{x: null}` and as a maintainer of a popular library, which previously followed that model, and now follows the "a string-to-string(s) multimap" with extensions, we have now introduced understandable pain.

Since I think we prefer to follow the standard, my only hope for those users was to propose some kind of change to the standard.

From my point of view, introducing layered interpretations doesn't help that much when everyone has their own bespoke concept of what a layer should be like - the entire point of standards is to standardise the approach so we don't end up with people building N different ways of representing null values etc. Again, I don't have a strong opinion about it, but this is the pain point and I'm just bringing it up and starting the discussion on behalf of the affected users/developers.

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

Message ID: <whatwg/url/issues/732/1370840176@github.com>