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
OMG ... protobuf generated code has a json tag that uses snake_case AND a protobuf tag that uses camel case:
// REQUIRED.// The list of app providers which can open this mime typeAppProviders []*ProviderInfo`protobuf:"bytes,4,rep,name=app_providers,json=appProviders,proto3" json:"app_providers,omitempty"`
Generation of the json tags was a historical mistake. If we could go back in time, we would not have generated it. It gives the illusion that protobuf messages work correctly with encoding/json, but they don't.
OMG ... protobuf generated code has a json tag that uses snake_case AND a protobuf tag that uses camel case:
But the json tag and encoding/json should not be used:
Unfortunately, we are using
encoding/json
all over the place. google.golang.org/protobuf/encoding/protojson should be used.AFAICT that would change all the generated json clients rely on ... 😞
The text was updated successfully, but these errors were encountered: