You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
OpenApiSpecGeneratorPlugin omits parameters and response headers from generated specs #2032
OpenApiSpecGeneratorPlugin never emits query, header or path parameters, or response headers, in generated OpenAPI specs.
Since the move to Microsoft.OpenApi 3.x, collection properties such as OpenApiOperation.Parameters, OpenApiPathItem.Parameters and OpenApiResponse.Headers are null by default. The plugin adds to them with null-conditional calls, so every addition is a silent no-op:
Generated specs list the query, header and path parameters, and the response headers, observed in recorded traffic.
Actual behaviour
Operations have no parameters and responses have no headers.
Steps to reproduce
Enable OpenApiSpecGeneratorPlugin and watch an API.
Record requests that use query string parameters, custom request headers and parametrized paths (for example /users/123?$select=name), and whose responses include headers.
Stop recording and open the generated spec. Parameters and response headers are missing.
Fix: initialize the collections (for example Parameters = [], Headers = new Dictionary<string, IOpenApiHeader>()) or use ??= before adding. Add tests that cover parameters and response headers in generated specs.
Activity