Feature request checklist
Change
Allow for the protobuf field name mapping to use the JSONName instead of the field names.
Example
person.firstName vs. person.first_name
Alternatives considered
I have temporarily forked this repo to support this, it was a pretty simple change, however I am not sure of a good way to make this configurable either through a global var or a build tag for a PR.
master...Blizzard:cel-go:blizzard
Ideally I don't want to maintain this for for such a small thing. The reason why this is needed in our use case is that we allow for CEL queries to filter data in a graphql API. With the graphql schema being based on the JSON of the data, it is way less confusing to our users than having to do the mental dance of the above example.
Feature request checklist
Change
Allow for the protobuf field name mapping to use the JSONName instead of the field names.
Example
person.firstNamevs.person.first_nameAlternatives considered
I have temporarily forked this repo to support this, it was a pretty simple change, however I am not sure of a good way to make this configurable either through a global var or a build tag for a PR.
master...Blizzard:cel-go:blizzard
Ideally I don't want to maintain this for for such a small thing. The reason why this is needed in our use case is that we allow for CEL queries to filter data in a graphql API. With the graphql schema being based on the JSON of the data, it is way less confusing to our users than having to do the mental dance of the above example.