[GitHub] [airavata-custos] dinukadesilva opened a new issue #143: Is there any reason behind following snake case in JSON responses

[GitBox <gi...@apache.org>]

dinukadesilva opened a new issue #143:
URL: https://github.com/apache/airavata-custos/issues/143


   I wonder why the API responses do not follow the camel case instead of the snake case in the JSON properties.
   
   https://en.wikipedia.org/wiki/Naming_convention_(programming)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [airavata-custos] isururanawaka commented on issue #143: Is there any reason behind following snake case in JSON responses

[GitBox <gi...@apache.org>]

isururanawaka commented on issue #143:
URL: https://github.com/apache/airavata-custos/issues/143#issuecomment-806851778


   Hi Dinuka, proto3 style guide suggests to write in snake case for field names. https://developers.google.com/protocol-buffers/docs/style. Anyway, json convention is done at envoy proxy so it converts those fields to snake case


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [airavata-custos] isururanawaka closed issue #143: Is there any reason behind following snake case in JSON responses

[GitBox <gi...@apache.org>]

isururanawaka closed issue #143:
URL: https://github.com/apache/airavata-custos/issues/143


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org