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
I wonder if there is any documentation for the JSON entities returned by the XQueue endpoints?
So far the best I can do is reverse engineering. I was surprised to see JSON objects embedded in JSON strings. What is the motivation for doing that? The drawbacks of this solution are that:
it makes it harder to define a proper JSON schema for these entities (consequently, it makes it impossible to decode these entities with automated solutions based on such schemas),
entities have to be parsed several times,
entities take more space because they are escaped several times,
pretty printing an entity is hopeless.
Why not use plain old JSON objects instead?
To be clearer, I propose that we replace the following schema:
{
"foo": "{ \"bar\": \"baz\" }"
}
With this one:
{
"foo": {
"bar": "baz"
}
}
The text was updated successfully, but these errors were encountered:
I wonder if there is any documentation for the JSON entities returned by the XQueue endpoints?
So far the best I can do is reverse engineering. I was surprised to see JSON objects embedded in JSON strings. What is the motivation for doing that? The drawbacks of this solution are that:
Why not use plain old JSON objects instead?
To be clearer, I propose that we replace the following schema:
With this one:
The text was updated successfully, but these errors were encountered: