feat: add option to control using proto text name as key during URL encoding #3311
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.
Description (what this PR does / why we need it):
binding.EncodeURL
andform.EncodeValues
andform.EncodeFieldMask
addoption.EncodeOption
, used to control whether to use proto text name as key when encoding. and it will not affect the original logiccmd/protoc-gen-go-http
add the-prototext_encodeurl
parameter to control whether to use the json tag defined in proto as the key when encoding. The default is false and will not change the original generated code logic. (example:kratos proto client api/test.proto -- --go-http_opt=prototext_encodeurl=true
)Which issue(s) this PR fixes (resolves / be part of):
resolves: #3141
resolves: #2761
Other special notes for the reviewers: