You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RapidJSON currently implements RFC4627, which has been superseeded by RFC7159 in March 2014.
Among mostly editorial changes, the most important update is:
Changed the definition of "JSON text" so that it can be any JSON
value, removing the constraint that it be an object or array.
(This effectively closes Optionally accept arbitrary root elements #21 and issue80.)
RapidJSON seems to be compliant with the other changes already, AFAICS.
If you want to keep strict RFC4627-compliancy available, we could add a RAPIDJSON_RFC4627 macro to enforce the object/array top-level requirement. An AcceptAnyRoot API as proposed by #21 is then no longer needed.
The text was updated successfully, but these errors were encountered:
RapidJSON currently implements RFC4627, which has been superseeded by RFC7159 in March 2014.
Among mostly editorial changes, the most important update is:
value, removing the constraint that it be an object or array.
(This effectively closes Optionally accept arbitrary root elements #21 and issue80.)
RapidJSON seems to be compliant with the other changes already, AFAICS.
If you want to keep strict RFC4627-compliancy available, we could add a
RAPIDJSON_RFC4627
macro to enforce the object/array top-level requirement. AnAcceptAnyRoot
API as proposed by #21 is then no longer needed.The text was updated successfully, but these errors were encountered: