Currently, the documentation has snake cased fields in the .proto according to the protocol buffers style guide. Then, in the documentation .rst files, the same fields are camelCased. The Avro had originally been in camel case, and the signatures of fields have been left that way throughout the API. The serialized JSON that results from the protocol buffers messages is camel cased, and so this split has been maintained.
However, we ought to change the camelCased fields to snake case to improve consistency of the documentation, while the details of JSON serialization are covered in the appendix. @mbaudis
Currently, the documentation has snake cased fields in the
.protoaccording to the protocol buffers style guide. Then, in the documentation.rstfiles, the same fields are camelCased. The Avro had originally been in camel case, and the signatures of fields have been left that way throughout the API. The serialized JSON that results from the protocol buffers messages is camel cased, and so this split has been maintained.However, we ought to change the camelCased fields to snake case to improve consistency of the documentation, while the details of JSON serialization are covered in the appendix. @mbaudis