-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
Fix copy-paste "format: binary" error #4294
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -1800,17 +1800,17 @@ requestBody: | |||||
schema: | ||||||
type: object | ||||||
properties: | ||||||
# default for a string without `contentEncoding` is `text/plain` | ||||||
id: | ||||||
# default for primitives without a special format is text/plain | ||||||
type: string | ||||||
format: uuid | ||||||
profileImage: | ||||||
# default for string with binary format is `application/octet-stream` | ||||||
type: string | ||||||
format: binary | ||||||
|
||||||
# default for a schema without `type` is `application/octet-stream` | ||||||
profileImage: {} | ||||||
|
||||||
# default for arrays is based on the type in the `items` | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. and
Suggested change
|
||||||
# subschema, which is an object, so `application/json` | ||||||
addresses: | ||||||
# default for arrays is based on the type in the `items` | ||||||
# subschema, which is an object, so `application/json` | ||||||
type: array | ||||||
items: | ||||||
$ref: '#/components/schemas/Address' | ||||||
|
@@ -1828,31 +1828,27 @@ requestBody: | |||||
schema: | ||||||
type: object | ||||||
properties: | ||||||
# No Encoding Object, so use default `text/plain` | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. and
Suggested change
|
||||||
id: | ||||||
# default is `text/plain` | ||||||
type: string | ||||||
format: uuid | ||||||
|
||||||
# Encoding Object overrides the default `application/json` | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. and maybe
Suggested change
|
||||||
# for each item in the array with `application/xml; charset=utf-8` | ||||||
addresses: | ||||||
# default based on the `items` subschema would be | ||||||
# `application/json`, but we want these address objects | ||||||
# serialized as `application/xml` instead | ||||||
description: addresses in XML format | ||||||
type: array | ||||||
items: | ||||||
$ref: '#/components/schemas/Address' | ||||||
profileImage: | ||||||
# default is application/octet-stream, but we can declare | ||||||
# a more specific image type or types | ||||||
type: string | ||||||
format: binary | ||||||
|
||||||
# Encoding Object accepts only PNG or JPEG, and also describes | ||||||
# a custom header for just this part in the multipart format | ||||||
profileImage: {} | ||||||
|
||||||
encoding: | ||||||
addresses: | ||||||
# require XML Content-Type in utf-8 encoding | ||||||
# This is applied to each address part corresponding | ||||||
# to each address in he array | ||||||
contentType: application/xml; charset=utf-8 | ||||||
profileImage: | ||||||
# only accept png or jpeg | ||||||
contentType: image/png, image/jpeg | ||||||
headers: | ||||||
X-Rate-Limit-Limit: | ||||||
|
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we instead say:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mikekistler no, because
text/plain
is a content type (Encoding ObjectcontentType
, or alternatively Schema ObjectcontentMediaType
) and not a content encoding (Schema ObjectcontentEncoding
, or alternatively Encoding Objectheaders
field, headerContent-TransferEncoding
) which is something like"base64"
But we could say:
# default content type for a string without `contentEncoding` is `text/plain`
so I'll do that. I totally see how you read it the way you did and I had to think a moment before realizing what was wrong with it.