Skip to content

v3.1 - contentEncoding #3230

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

Closed
commonism opened this issue Apr 5, 2023 · 2 comments · Fixed by #3233
Closed

v3.1 - contentEncoding #3230

commonism opened this issue Apr 5, 2023 · 2 comments · Fixed by #3233
Labels
examples requests for more or better examples in the specification media and encoding Issues regarding media type support and how to encode data (outside of query/path params)
Milestone

Comments

@commonism
Copy link
Contributor

The example from the spec:

          profileImage:
            # Content-Type for application-level encoded resource is `text/plain`
            type: string
            contentMediaType: image/png
            contentEncoding: base64

contradicts the specification:

  • If the property is a type: string with a contentEncoding, the default Content-Type is application/octet-stream

Henry Andreews agrees

@MikeRalphson
Copy link
Member

Thank you. Do you have time to raise a PR against version 3.1.1?

@handrews handrews added this to the v3.1.1 milestone Jan 27, 2024
@handrews handrews added examples requests for more or better examples in the specification media and encoding Issues regarding media type support and how to encode data (outside of query/path params) and removed 3.1.patch labels Jan 27, 2024
@handrews
Copy link
Member

Fix was accepted and merged- not sure why we didn't close this earlier.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
examples requests for more or better examples in the specification media and encoding Issues regarding media type support and how to encode data (outside of query/path params)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants