UI: Composite schema is not expandable on endpoint edit | Voters

UI: Composite schema is not expandable on endpoint edit

Dmytro Bardai

A composite schema is not expandable on the endpoint edit page. It could be more usable to be able to expand it in the way similar when the composition is defined directly on the edit page. See screenshots attached for a clarity.

October 22, 2024

Ian Paterson

In my use case it would be terrific to be able to define a subset of a composite schema. For a simple example, you might have a Product schema with full product detail, but in certain contexts you only get a PartialProduct that has the minimal data needed to display in a product catalog. 
That seems like a complicated thing to pull off. Currently if you attempt to hack overrides on a composite schema the Apidog UI shows the error "The referenced data schema Product is not of type object, it will be ignored." For example where #/definitions/4205172 is a composite "allOf" schema: 
{
"type": "object",
"x-apidog-refs": {
"01JD86H4XBEE4QQZKXZR2FS8MR": {
"$ref": "#/definitions/4205172",
"x-apidog-overrides": {
"id": null,
"type": null
}
}
},
"x-apidog-orders": [
"01JD86H4XBEE4QQZKXZR2FS8MR"
],
"properties": {}
}