Skip to content

Issues: OAI/OpenAPI-Specification

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clear current search query, filters, and sorts
11 Open 154 Closed
11 Open 154 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Assigned to nobody Loading
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Provide guidance on using OAS with Overlay and Arazzo clarification requests to clarify, but not change, part of the spec
#4221 opened Nov 21, 2024 by handrews v3.1.2
2
The Response object's default field is confusing and inconsistently interpreted clarification requests to clarify, but not change, part of the spec re-use: globals/defaults Default or global components that can be overridden in some way
#3396 opened Oct 5, 2023 by ahl
9
Are these OpenAPI 3 paths ambiguous? clarification requests to clarify, but not change, part of the spec question request matching Matching requests to URL templates, media types, etc.
#2564 opened May 4, 2021 by bfreuden
7
Clarification required for templated paths with same hierarchy but different templated names and methods clarification requests to clarify, but not change, part of the spec request matching Matching requests to URL templates, media types, etc.
#2530 opened Apr 9, 2021 by Jmcleodfoss
1
Ordering of matches when no path is concrete clarification requests to clarify, but not change, part of the spec request matching Matching requests to URL templates, media types, etc.
#2356 opened Sep 21, 2020 by JonnySpruce
5
More example same hierarchy in path templating clarification requests to clarify, but not change, part of the spec examples requests for more or better examples in the specification request matching Matching requests to URL templates, media types, etc.
#2015 opened Sep 25, 2019 by ota42y
1
Path Templating with multiple parameters allows for ambiguous parsing clarification requests to clarify, but not change, part of the spec request matching Matching requests to URL templates, media types, etc.
#1970 opened Jul 8, 2019 by richardwhiuk
3
Components fields name too restrictive? clarification requests to clarify, but not change, part of the spec examples requests for more or better examples in the specification
#1387 opened Oct 23, 2017 by PerthCharern
2
Inconsistency in runtime expression examples for request headers clarification requests to clarify, but not change, part of the spec
#1323 opened Aug 17, 2017 by hkosova
1
Clarification on the purpose of the API license? clarification requests to clarify, but not change, part of the spec editorial Wording and stylistic issues review
#726 opened Jul 7, 2016 by harrisj
16
oauth and basic security are allowed to be used together. clarification requests to clarify, but not change, part of the spec security: auth Authentication including overlap with authorization security
#620 opened Apr 4, 2016 by jsdevel
8
ProTip! Updated in the last three days: updated:>2025-05-26.