Add openapiv2_json_name field option to specify non alphanumeric characters in JSON property name #686
+249
−174
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
…acters in JSON property name proto3 provides json_name option by default (see also https://developers.google.com/protocol-buffers/docs/proto3#json) but we cannot use this option because it converts snake_cased field name to camelCased one. It means we should have our own json_name field option for this purpose to keep backward compatibility.
co3k
force-pushed
the
support_json_name_field_tag
branch
from
077457a
to
705dd8a
Compare
|
This is being considered in #546 |
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.
proto3 provides json_name option by default (see also https://developers.google.com/protocol-buffers/docs/proto3#json)
but we cannot use this option because it converts snake_cased field name to camelCased one. It means we should have
our own json_name field option for this purpose to keep backward compatibility.