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
By default, the generated jsonschema uses underscores, the same as the proto files. However, your other library, connect, by default uses camel case. The end result is that the generated schema does not actually match what connect expects.
Is there a way to configure the json encoder?
My use-case is as follows:
Use grpc & connect for APIs, this works well
We have a command which accepts a yaml file which gets serialized to proto and uploaded - think github actions definition. We want to publish a schema for just that file, so that editors can auto-complete appropriately.
The text was updated successfully, but these errors were encountered:
By default, the generated jsonschema uses underscores, the same as the proto files. However, your other library, connect, by default uses camel case. The end result is that the generated schema does not actually match what connect expects.
Is there a way to configure the json encoder?
My use-case is as follows:
The text was updated successfully, but these errors were encountered: