Remove JsonGen base64 encoding basic option and keep only the URL safe encoding #391
Conversation
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
…e encoding. Motivation: Legacy Buffer base64 encoding stemming from Vert.x 3 is dropped in Vert.x 5 Changes: Remove the base64Type member of the @JsonGen annotation and the related handling in the generator and use URL base 64. Result: The generated converter only encode/decode buffers against URL base 64.
|
Nice! |
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.
Motivation:
Legacy Buffer base64 encoding stemming from Vert.x 3 is dropped in Vert.x 5
Changes:
Remove the base64Type member of the
@JsonGenannotation and the related handling in the generator and use URL base 64.Result:
The generated converter only encode/decode buffers against URL base 64.
Motivation:
Explain here the context, and why you're making that change, what is the problem you're trying to solve.