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
As pointed out by @lmars in #3 (comment) "Publish JSON serializable object", we're perhaps not clear enough that 'plain objects' can be (semi-)transparently encoded to and decoded from JSON in our SDKs for message data.
This is discrete and different from our support for JSON or MessagePack in the protocol.
Work on this issue includes deciding whether new feature node(s) are required, or whether this capability can be included or better defined within the scope of an existing feature node or nodes.
The text was updated successfully, but these errors were encountered:
As pointed out by @lmars in #3 (comment) "Publish JSON serializable object", we're perhaps not clear enough that 'plain objects' can be (semi-)transparently encoded to and decoded from JSON in our SDKs for message
data
.Relevant terminology from the features spec:
JsonObject
orJsonArray
like objectEspecially relevant are: RSL4c, RSL4d, TM2d, TP3e.
This is discrete and different from our support for JSON or MessagePack in the protocol.
Work on this issue includes deciding whether new feature node(s) are required, or whether this capability can be included or better defined within the scope of an existing feature node or nodes.
The text was updated successfully, but these errors were encountered: