Skip to content

Conversation

handrews
Copy link
Member

Addresses #3710 (comment) – If this is approved I will port it to 3.1.1 and 3.2.0.

If no Encoding Object is provided, the behavior is the same as an empty Encoding Object, as none of its fields are required.

If no Encoding Object is provided, the behavior is the same as
an empty Encoding Object, as none of its fields are required.
@handrews handrews added the param serialization Issues related to parameter and/or header serialization label Apr 19, 2024
@handrews handrews requested a review from a team April 19, 2024 19:44
@handrews handrews added the clarification requests to clarify, but not change, part of the spec label Apr 19, 2024
@handrews handrews added this to the v3.0.4 milestone Apr 19, 2024
@lornajane lornajane requested a review from mikekistler May 1, 2024 07:06
Copy link
Contributor

@mikekistler mikekistler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! 👍

@handrews
Copy link
Member Author

handrews commented May 1, 2024

Two TSC members have approved, therefore I'm merging.

@handrews handrews merged commit def3109 into OAI:v3.0.4-dev May 1, 2024
@handrews handrews deleted the default-encoding-object branch May 1, 2024 19:51
miqui added a commit that referenced this pull request May 9, 2024
Explain default Encoding Object behavior (3.2.0 port of #3719)
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