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
My requirement is that when generating PHP code via protobuf and using: serializeToJsonString directly,
if json_name is not defined, it will produce camel case. It looks like this: user_name -> userName.
The text was updated successfully, but these errors were encountered:
flc1125
changed the title
feature:[buf lint] You want to add validation that supports json name to be lowercase
feature:[buf lint] Add validation that supports json_name to be lowercase
Apr 30, 2024
bufdev
changed the title
feature:[buf lint] Add validation that supports json_name to be lowercase
Add linter that enforces that json_name values are lower_snake_case
May 18, 2024
Thanks for your request here. It's a fair issue, but we'll have to consider the implications. We are working on the ability to write custom lint plugins at the moment, and this may be a good candidate for a custom lint rule implemented outside of buf, given that there may not be a good consensus as to what style json_name values should be in. We'll keep this issue open as we work on custom lint plugins, and will keep you updated.
We're cleaning up our issues, and we're going to close this as a "duplicate" of #29 - we're actively working on #29, so I'd encourage you to watch that issue for updates!
My requirement is that when generating PHP code via protobuf and using:
serializeToJsonString
directly,if
json_name
is not defined, it will produce camel case. It looks like this:user_name
->userName
.The text was updated successfully, but these errors were encountered: