Replies: 1 comment 1 reply
|
One advantage of using the data as dictionary - with a Think of streaming the flight number and airline as: and giving the price a little bit later like this: ... this makes it possible to merge the resulting data. If it wouldn't be a dictionary - you would have to define how appending (merging?!) them should look like. IMHO having it as dictionary is fine. If you want to put anything else into it give it a good key :). What do you think? |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
If I'm reading the definition of the DataPart schema correctly, then the
dataproperty is typed as a JSON object. This leads to a couple of questions:datashould be allowed to be either an object or an array.datatyped as to allow any JSON root element? Once upon a time JSON restricted the root to object and array, but that hasn't been true since RFC 7159.Assuming we are restricted to just producing JSON objects, what is the intended way to transmit other outputs? Should an array be broken down into one Part per item? What if the items are not themselves JSON object values? Sorry if this is all obvious, but I couldn't find any clear explanation of the intent here.
All reactions