How to express content=all and content=base in the schema

[mkettrick]

In looking at the schema, I see the "BatchFormat" parameter where "base" and "all" are enumerated but I don't see how ?content=base (and no content query parameter) points to /definitions/device and ?content=all points to /definitions/DeviceContentAll.

Per a comment from Mark during the review of the document: "Need to add to the schema somehow. I think the example given therein is for content=all"

[ondrejtomcik]

Schema contains two examples. GET /api/v1/devices returns payload equivalent to content=base while GET /api/v1/devices/{deviceId} returns payload equivalent to content=all, what is also written in the description of that payload. There is no way how to affect example based on the query parameter unfortunately.

[mkettrick]

Mark, do you have any ideas for this? Ideally, the CTT can use the schema to validate content=base vs. content=all. If not, this will have to be hard-coded in the CTT.

[ondrejtomcik]

@mkettrick I would close this issue and as you wrote, hardcode it.

[mkettrick]

I thought it was agreed that the schema would change. At least that's what I gathered from the meeting minutes and Mark's comments. Is hard coding this in the CTT the final decision agreed by all?

[ondrejtomcik]

I am just saying that the swagger model cannot be visualized based on the query parameter in the swagger ui. Issue is about expressing two different data models based on the query parameters, what is not in the swagger possible.