[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#46486: [External] : bug#46486: 28.0.50; json-parse-string missing su
|
From: |
Drew Adams |
|
Subject: |
bug#46486: [External] : bug#46486: 28.0.50; json-parse-string missing support for key-less json strings |
|
Date: |
Sat, 13 Feb 2021 23:22:43 +0000 |
> OTOH, RFC 8259 does seem to allow any value type at the toplevel now,
> so we might as well support this. I don’t have a strong opinion here.
> Using RFC 4627 semantics seems a bit safer and more conservative, but
> given that it’s considered obsoleted by RFC 8259, maybe we should
> switch to the semantics of the newer standard.
Sorry, my previous comment duplicates what you just said.
IMO, nowadays applications should generally
consider all possible JSON values as JSON
texts: objects, arrays, and scalars.