openapi-generators / openapi-generators/openapi-python-client
Support for multiple content types in error response
还没有人认领这个 Issue。
- 主要语言
- Python
- 星标
- 2k
- 派生
- 293
- 平均合并
- 34 分钟
- 30 天内合并 PR
- 1
描述
Describe the bug
Similar to previous issues about multiple content types support like https://github.com/openapi-generators/openapi-python-client/issues/453 or https://github.com/openapi-generators/openapi-python-client/issues/1004
For a single endpoint, the same error code can be returned by different piece of software. For example, an application can return error details as application/json but have some infra elements in front (cloud gateway/load balancer/reverse proxy/firewall) that can block request and also return their own errors in their own format text/json/xml (usually for network errors 401,403,502,503,504).
In my use case, I realized a firewall can sometimes block requests and returns a text/plain with a string Access Forbidden. So I'm trying to represent that in my OpenAPI spec so the generated client can handle these errors properly without crashing, and this works for some of the other openapi generators. But it doesn't work well with this python client, because the content type is not validated in the generated code. It only depends on the first content declared in the schema and seems to ignore the other ones.
So I'm getting the following implementation:
if response.status_code == 403:
response_403 = APIError.from_dict(response.json())
Which works for json error, but json parsing throw an exception if it's something else (like text/plain)
And if I declare text/plain before application/json, I get:
if response.status_code == 403:
response_403 = response.text
But in that case, I'm losing any detail about the json error.
What I expect here, is something similar to the oapi-codegen golang implementation.
If there are multiple content types defined for an error code, check that the response content type match before handling it.
So each content type can coexist and be handled separately.
case strings.Contains(rsp.Header.Get("Content-Type"), "json") && rsp.StatusCode == 403:
// this is a json error
var dest APIError
if err := json.Unmarshal(bodyBytes, &dest); err != nil {
return nil, err
}
response.JSON403 = &dest
case rsp.StatusCode == 403:
... // default case for text/plain error
OpenAPI Spec File
403:
description: Forbidden
content:
application/json:
schema:
$ref: '#/components/schemas/APIError'
text/plain:
schema:
type: string
Desktop (please complete the following information):
- OS: macOS 14.7.4
- Python Version: 3.11.88
- openapi-python-client version: 0.24.3
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
使用提供的、包含 application/json 和 text/plain 的 OpenAPI 403 响应,复现生成客户端当前的处理方式。检查生成客户端的错误响应路径,并在可用时运行相关的客户端生成和响应测试。完成的标准是,生成客户端根据响应的 Content-Type 选择处理方式,从而在不尝试将 text/plain 解析为 JSON 的情况下仍能保留 JSON 详情。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- python
- 领域
- api
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 45/100