It is more common to have a wrapper in the form of {type,value} than {type:value} so it makes sense to align WRAPPING_OBJECT on this or to drop it (which is more than fine for me too if there is no consensus on that). It means we can drop format and just support implicitly PROPERTY in next release. Long story short current definition is not mainstream enough IMHO and API is not generic enough (format) too. If we make the API generic enough we get back on serializer/deserializers so it is probably not worth it for end users so let's keep it simple for next release.
Verdent
commented
2 years ago
It is more common to have a wrapper in the form of
{type,value}than{type:value}so it makes sense to alignWRAPPING_OBJECTon this or to drop it (which is more than fine for me too if there is no consensus on that). It means we can drop format and just support implicitlyPROPERTYin next release. Long story short current definition is not mainstream enough IMHO and API is not generic enough (format) too. If we make the API generic enough we get back on serializer/deserializers so it is probably not worth it for end users so let's keep it simple for next release.