Closed ioquatix closed 3 months ago
Fixes https://github.com/socketry/protocol-http/issues/56.
We could accept nil keys, but there is no way to reasonably format it, e.g. consider {nil => {nil => "foo"}} would format, hypothetically, as []=foo which would decode as {nil => ["foo"]}. I can't see any way to disambiguate the situation.
nil
{nil => {nil => "foo"}}
[]=foo
{nil => ["foo"]}
Fixes https://github.com/socketry/protocol-http/issues/56.
We could accept
nilkeys, but there is no way to reasonably format it, e.g. consider{nil => {nil => "foo"}}would format, hypothetically, as[]=foowhich would decode as{nil => ["foo"]}. I can't see any way to disambiguate the situation.Types of Changes
Contribution