Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

v3.2.1 release

未关闭
  • 哪里不对？
#5,460 11 条评论 1 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@lornajane 已经在做这个了。

开始于 2026年9月10日。

评估

这个 Issue 还没有评估数据。

描述

This issue requires TSC signoff in order to complete.

  • schema changes since last schema release (2025-11-23) consist of various fixes to be better aligned with the specification:

    • contentType format fix (now allows comma-separated values)
    • propertyName is required in the discriminator object
    • ABNF applied for path parameter names, header names, request method names
    • style, explode, allowReserved existence and defaults now better enforced
    • adjacent query, querystring parameters are prohibited

  • spec changes since 3.2.0 release:

    • more cross-references to RFCs and other sections of the specification
    • clarification of how paths are matched when a template variable contains a "/"
    • corrections to the table of Style Examples (used in parameter encoding)
    • we now explicitly note more in/style/explode combinations that are prohibited, namely:
      • in: cookie, style: form, explode: false with arrays or objects
      • style: form, explode: true with arrays or objects in encoding objects (application/x-www-form-urlencoded or multipart/* message bodies)
    • corrections to descriptions of how encoding objects are used, such as the use of prefixEncoding and itemEncoding with data modelled as an array, and usage of contentType together or separately from a Content-Type header in a message part
    • addition of an ABNF for the encoding/<name>/contentType field
主要语言
Markdown
星标
31.2k
派生
9.2k
平均合并
2 天 9 小时
30 天内合并 PR
17

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

OAI/OpenAPI-Specification 的其他 Issue

查看 OAI/OpenAPI-Specification 的全部 Issue

把新 issue 发到你的邮箱

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