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
Message field names are mapped to lowerCamelCase and become JSON object keys. If the json_name field option is specified, the specified value will be used as the key instead. Parsers accept both the lowerCamelCase name (or the one specified by the json_name option) and the original proto field name
While parsers should accept both, most libraries (for other languages) output lowerCamelCase as a default, so we decided to use that
It seems that in generated HTTP server, fields of messages are renamed to camel case. Is this a feature?
The text was updated successfully, but these errors were encountered: