JSON parser uses field's name as-is, even when it's in snake_case

[vasyafromrussia]

proto3 spec says:

By default proto3 JSON printer should convert the field name to lowerCamelCase and use that as the JSON name. An implementation may provide an option to use proto field name as the JSON name instead. Proto3 JSON parsers are required to accept both the converted lowerCamelCase name and the proto field name.

However, generated data classes use snake case json keys, and there's no way to configure this behaviour. I.e. if my service is implemented respectively to specs, I cannot parse service's responses.

I suppose, json names must be converted to camel case in generated client.