telescope: Incorrect casing on cosmos LCD query response types

I’m pretty ignorant of the mechanics of proto generation, and am not positive this is a telescope issue. I’m also working with the upcoming .46 cosmos release, which might be relevant

Basically, I have a repo (https://github.com/haveanicedavid/groups-ui) which is using a package (https://github.com/haveanicedavid/cosmos-groups-ts) generated through telescope, where I

1. pulled down the latest tagged SDK .46 release (v0.46.1)
2. copied the proto tags over from /proto in SDK to /proto in the telescope proj
3. pulled in missing proto files from the buf registry (buf export buf.build/cosmos/cosmos-sdk:$(curl -sS https://api.github.com/repos/cosmos/cosmos-sdk/commits/v0.46.1 | jq -r .sha) --output ./proto in the telescope proj)
4. ran the codegen script yarn codegen (fixing proto errors til it runs correctly) and published to NPM

With that, i’ve been able to generate an LCD client through the factory and successfully run queries, and the shape of response data on those queries is correct, but the casing is off because LCD / REST sends properties in snake_case. For example the GroupInfo interface:

compared to the response (totalWeight vs total_weight, created_at vs createdAt):

Again, I’m not sure this is an issue with telescope or on my end (there are a lot of moving parts), but it seems like the response data for LCD / REST is structured as snake_case: https://docs.cosmos.network/master/modules/group/#rest so presumably this could impact all LCD query clients generated with cosmos protos