Skip to content
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

Jump to bottom

Port of last-minute 3.0.4 changes to 3.1.1 #4088

Merged
merged 6 commits into from
Sep 12, 2024
Merged

Port of last-minute 3.0.4 changes to 3.1.1 #4088

merged 6 commits into from
Sep 12, 2024

Conversation

handrews
Copy link
Member

@handrews handrews commented Sep 12, 2024 •
edited
Loading

handrews and others added 6 commits September 12, 2024 08:37
@handrews
Further guidance on RFC6570 and delimiters
11c5cac 
Also give Appendix C a better name because it is relevant
whether you are using an actual RFC6570 implementation or not.
@handrews
Further clarify link operation ambiguity
5c60e5b 
There are even more ways this can go wrong!
@handrews
Minor param serialization and wording fixes
ba08a1a 
* Explicitly set `explode: false` in an example as the default
  with `style: form` is `explode: true`; the `explode: true`
  example was also left explicit to reduce confusion.
* Tidy up overly conversational (e.g. "our document") language
  that I'd meant to revisit but forgot about.
* Include the Header Object as one of the places where the
  `style` keyword is used (even if it is the simplest case)
* Minor grammar fix.
* Fix a missing space before an RFC reference.
@handrews
Don't use both bold and italics
24b4ad3 
Style guide conformance.
@handrews
Clarify complete vs self-contained documents
19c7a46
@ralfhandl @handrews
Update versions/3.1.1.md
f1e0c28
@handrews handrews added links clarification requests to clarify, but not change, part of the spec param serialization Issues related to parameter and/or header serialization re-use: ref/id resolution how $ref, operationId, or anything else is resolved editorial Wording and stylistic issues labels Sep 12, 2024
@handrews handrews added this to the v3.1.1 milestone Sep 12, 2024
@handrews handrews requested a review from a team as a code owner September 12, 2024 15:41
@ralfhandl ralfhandl mentioned this pull request Sep 12, 2024
Closed
@ralfhandl ralfhandl requested a review from a team September 12, 2024 16:15
@lornajane lornajane merged commit 1fb38f6 into OAI:v3.1.1-dev Sep 12, 2024
2 checks passed
@handrews handrews deleted the last-311 branch September 12, 2024 20:02
ralfhandl added a commit to ralfhandl/OpenAPI-Specification that referenced this pull request Sep 13, 2024
@ralfhandl
Add OAI#4091, OAI#4088
06945d5
@ralfhandl ralfhandl mentioned this pull request Sep 13, 2024
Closed
@ralfhandl ralfhandl mentioned this pull request Sep 30, 2024
Merged
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ralfhandl ralfhandl ralfhandl approved these changes

@lornajane lornajane lornajane approved these changes

Assignees
No one assigned
Labels
clarification requests to clarify, but not change, part of the spec editorial Wording and stylistic issues links param serialization Issues related to parameter and/or header serialization re-use: ref/id resolution how $ref, operationId, or anything else is resolved
Projects
None yet
Milestone
v3.1.1
Development

Successfully merging this pull request may close these issues.
3 participants
@handrews @lornajane @ralfhandl