You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Guys, I noticed an issue when I enable json_names_for_fields=true.
It does generate JSON camel case fields in a swagger doc, but except fields which were defined in URLs, like the following:
…osystem#985)
* Use json name when GetUseJSONNamesForFields is enabled
* Optimzed an if statement
* Merge two if statements
* Convert parameters to lower camel case in url
* Revert services.go file
* Fix an unit test
* Update bazel file
* Add an unit test for testing json camel case
* Add an unit test for testing code without enabling json camel case
* Add more corner cases
Fixesgrpc-ecosystem#986
Hi Guys, I noticed an issue when I enable
json_names_for_fields=true
.It does generate JSON camel case fields in a swagger doc, but except fields which were defined in URLs, like the following:
The swagger that generated by the above proto included the snake case
abc_id
even with enablingjson_names_for_fields=true
.What did you expect to happen instead:
Expect
abcId
instead ofabc_id
in the generated swagger doc.What's your theory on why it isn't working:
It seems the swagger generator did not convert those snake case fields when rendering the template.
The text was updated successfully, but these errors were encountered: