Yes. RFC 4627 only allowed json text to be either object or array. RFC 7159 extended it's definition to include any value. Look at https://tools.ietf.org/html/rfc7159#page-15
Quoting that page,
"Changed the definition of "JSON text" so that it can be any JSON value, removing the constraint that it be an object or array."
https://tip.golang.org/pkg/encoding/json/ mentions RFC 4627. The RFC 4627 is obsolete by RFC 7159.
It looks like current implementation already confirms to RFC 7159. https://play.golang.org/p/lY-b3Ia13k
Should we update the rfc no in the docs?
The text was updated successfully, but these errors were encountered: