Skip to content
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.

Sign up for GitHub

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

Jump to bottom

fix(oas): serialize binary and base64 data #190

Merged
merged 8 commits into from
Feb 28, 2023
Merged

fix(oas): serialize binary and base64 data #190

merged 8 commits into from
Feb 28, 2023

Conversation

derevnjuk
Copy link
Member

fixes #181

@derevnjuk derevnjuk added the Type: bug Something isn't working. label Feb 22, 2023
@derevnjuk derevnjuk self-assigned this Feb 22, 2023
@codeclimate
Copy link

codeclimate bot commented Feb 22, 2023 •
edited
Loading

Code Climate has analyzed commit abba161 and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 95.8% (50% is the threshold).

This pull request will bring the total coverage in the repository to 91.8% (0.0% change).

View more on Code Climate.

@derevnjuk derevnjuk changed the title fix(oas): setting the Content-Transfer-Encoding header to base64 fix(oas): sampling binary and base64 formats Feb 22, 2023
@derevnjuk derevnjuk force-pushed the fix-#181/unexpected_Content-Transfer-Encoding_header_for_some_multipart_data branch 2 times, most recently from e74c64b to 759ae63 Compare February 24, 2023 09:08
@derevnjuk derevnjuk changed the title fix(oas): sampling binary and base64 formats fix(oas): serialize binary and base64 formats Feb 24, 2023
@derevnjuk derevnjuk changed the title fix(oas): serialize binary and base64 formats fix(oas): serialize binary and base64 data Feb 24, 2023
@derevnjuk derevnjuk force-pushed the fix-#181/unexpected_Content-Transfer-Encoding_header_for_some_multipart_data branch from 759ae63 to f778332 Compare February 24, 2023 10:25
@derevnjuk derevnjuk force-pushed the fix-#181/unexpected_Content-Transfer-Encoding_header_for_some_multipart_data branch from f778332 to 8584463 Compare February 24, 2023 10:42
@derevnjuk derevnjuk marked this pull request as ready for review February 24, 2023 10:46
@derevnjuk derevnjuk enabled auto-merge (squash) February 24, 2023 10:47
@derevnjuk derevnjuk force-pushed the fix-#181/unexpected_Content-Transfer-Encoding_header_for_some_multipart_data branch 2 times, most recently from 16a5504 to 60e1c33 Compare February 24, 2023 16:15
@derevnjuk derevnjuk force-pushed the fix-#181/unexpected_Content-Transfer-Encoding_header_for_some_multipart_data branch from 60e1c33 to f83eb70 Compare February 24, 2023 16:18
@derevnjuk derevnjuk merged commit 88621b7 into master Feb 28, 2023
@derevnjuk derevnjuk deleted the fix-#181/unexpected_Content-Transfer-Encoding_header_for_some_multipart_data branch February 28, 2023 10:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@pmstss pmstss pmstss approved these changes

Assignees

@derevnjuk derevnjuk

Labels
Type: bug Something isn't working.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Unexpected Content-Transfer-Encoding header for some multipart data
2 participants
@derevnjuk @pmstss