Set OpenAPI Properties with GET /api/mgmnt/v1/:namespace/spec/:application/
When manually coding REST services and using
GET /api/mgmnt/v1/:namespace/spec/:application/ to return an OpenAPI spec, how do you specify supported properties (OpenAPI Properties in Use | Creating REST Services | InterSystems IRIS Data Platform 2021.1) like responses, definitions, and information in paths like summary and description?
GET /api/mgmnt/v1/:namespace/spec/:application/ | Creating REST Services | InterSystems IRIS Data Platform 2022.2
Using a very basic manual REST service that returns a JSON string I get a pretty basic spec that is not really helpful when it comes to documentation. I think the code-first approach would be useful for our purposes if we could make the resulting spec a bit more robust.
For context, I'm exploring the pros and cons of manual creation and spec first creation. Manual is simpler in terms of only needing a dispatch class to implement, but documentation becomes more cumbersome. Spec first creation is great on the documentation side, but when you are coding client-side it makes development process a bit more cumbersome. I have also looked at isc.rest.