v3.2: Provide guidance for multiple contentType values #4744
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We allow multiple `contentType` values in the Encoding Object, but do not provide any guidance on how to determine which to use when performing the encoding. This adds such guidance.
handrews
added
the
media and encoding
This was referenced Jun 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have always allowed multiple
contentTypevalues in the Encoding Object, but do not provide any guidance on how to determine which to use when performing the encoding. This adds such guidance.This has become more relevant with
multipart/mixedsupport, as the only way to define a set of parts where the order of the media types is not predictable (perhaps because the number of each media type is variable) is to useitemEncodingand put all of the media types incontentType.An example of this usage can be found in PR #4746.
(also fix a copy-paste error that left a
+at the beginning of a line)