Allow empty keys as defined in the JSON spec.

[umulmrum]

Hi,

the lib currenty disallows empty JSON keys although they are allowed by the JSON spec. I found several other libs with similar issues, where fixes have been suggested and pulled, so I'm quite confident it is correct to allow empty keys.

My use case worked with this fix although I'm not sure if there are other implications (tests do not cover this).

[ibarabash]

Hi @umulmrum ,

Thanks for contributing and hope you found this lib useful for you.
I'm not sure object's key could be empty according to specification RFC8259 https://tools.ietf.org/html/rfc8259 , ECMA-404 http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf :

An object structure is represented as a pair of curly brackets
surrounding zero or more name/value pairs (or members). A name is a
string. A single colon comes after each name, separating the name
from the value.

To ensure we are talking on same side: are we talking about object's key as about name of name/value pair?
Could you please send part of JSON of your use-case and link to spec you found object's key could be empty? Maybe your specific JSON doesn't follow standard and tries to use object in case where array is suitable? :)

[ibarabash]

Hm I found this one in ECMA-404:

The JSON syntax does not impose any restrictions on
the strings used as names, does not require that name strings be unique, and does not assign any
significance to the ordering of name/value pairs

So it allows following JSON:

{"": "value"}

Did you you mean this case @umulmrum ?