acacode / acacode/swagger-typescript-api

Not generating unions with multiple media types

未关闭
#314 2 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看
bug
主要语言
TypeScript
星标
4.1k
派生
436
PR 合并指标
30 天内没有已合并 PR

描述

There seems to be an issue generating union types when multiple media types exist that alter the requirements for the request body.

Example path with multiple media types ([right from the swagger requestBody docs](https://swagger.io/docs/specification/describing-request-body/)):

Given the following schema:
```yaml
paths:
/pets:
post:
summary: Add a new pet
requestBody:
content:
"application/json":
schema:
$ref: '#/components/schemas/Cat'
"application/foo.bar+json":
schema:
$ref: '#/components/schemas/Dog'
```

Only one output method will be generated, it seems to either be `application/json` or index 0, I'm not entirely sure.

Is there any way I can get this to generate a union type rather than always generating from schemas/Cat? It seems like the swagger specification should allow for multiple media types for a single endpoint.

> The requestBody is more flexible in that it lets you consume different media types, such as JSON, XML, form data, plain text, and others, and use different schemas for different media types. requestBody consists of the content object, an optional Markdown-formatted description, and an optional required flag (false by default). content lists the media types consumed by the operation (such as application/json) and specifies the schema for each media type

贡献指南

这个仓库没有索引到贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。