We found it useful for generated OpenAPI commands to retain runtime operation metadata so schema inspection can resolve mounted operations directly from the mounted spec.
The use case was:
- mounted OpenAPI-backed commands
- runtime schema lookup for a specific operation
- introspection of params, request body, and response shape
In our fork, we attached runtime operation metadata to generated commands so the framework could expose richer per-command schema information without relying on a stale baked manifest.
Reference patch:
Would you be open to upstreaming runtime OpenAPI metadata on generated commands so mounted operations can participate in schema introspection more cleanly?
We found it useful for generated OpenAPI commands to retain runtime operation metadata so schema inspection can resolve mounted operations directly from the mounted spec.
The use case was:
In our fork, we attached runtime operation metadata to generated commands so the framework could expose richer per-command schema information without relying on a stale baked manifest.
Reference patch:
Would you be open to upstreaming runtime OpenAPI metadata on generated commands so mounted operations can participate in schema introspection more cleanly?