Encoding Obj contentType takes a media range (3.0.4) #3813
Closed
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.
Fixes:
contentType
field: "comma-separated list of the two types"? #3739The "the two types" appears to have come from an example involving two types, and the TSC agrees that there was no intention to limit it to two. The syntax described also matches media type ranges, which is what is used for keys under
content
keywords that take objects of Media Type Objects. As that is analogous to the use ofcontentType
in the Encoding Object, this change aligns the wording.The guidance on default values was difficult to format in a readable way inside of the fixed fields table, so this change also moves it to its own table.