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.

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

Clarify allowEmptyValue -> disregard empty values (3.1.1 port of #3812) #3835

Merged
merged 1 commit into from
May 23, 2024

Conversation

handrews
Copy link
Member

This clarifies the meaning of allowEmptyValue as discussed in today'd TDC call. It is intended to indicate an agreement between the client and server to use zero-length string values as an indicator of unused fields.

This clarifies the meaning of `allowEmptyValue` as discussed in
today'd TDC call.  It is intended to indicate an agreement between
the client and server to use zero-length string values as an
indicator of unused fields.
@handrews handrews added clarification requests to clarify, but not change, part of the spec param serialization Issues related to parameter and/or header serialization labels May 21, 2024
@handrews handrews added this to the v3.1.1 milestone May 21, 2024
@handrews handrews requested a review from a team May 21, 2024 18:47
@lornajane lornajane merged commit d94d13f into OAI:v3.1.1-dev May 23, 2024
1 check passed
@handrews handrews deleted the disregard-empty-311 branch May 23, 2024 14:39
karenetheridge added a commit to karenetheridge/OpenAPI-Modern that referenced this pull request May 25, 2024
..now that its use has been clarified in v3.1.1 via OAI/OpenAPI-Specification#3835
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification requests to clarify, but not change, part of the spec param serialization Issues related to parameter and/or header serialization
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants