[FEATURE REQUEST] Global naming convention

With the introduction of the Custom GraphQL Root Fields and GraphQL Field Name features, one can specify the name used in the schema generation, for every field and table. This is very useful, especially, when referencing from client apps. But, this might become overhead for very large schemas, spanning across multiple Postgres schemas.

I would like to see a feature where one can specify the naming convention globally (perhaps at a schema level?), e.g. camelCase, PascalCase, etc.

This should be available for table names, field names, mutation names and relationship names.

Bonus Request:

• Would be even more amazing if we could define additional text to the naming convention, e.g. insert mutations: 'add'${PascalCase table name}
• Also be able to specify singular or plural in the convention, e.g. by_pk query name: ${singular camelCase table name} and normal select query: ${plural camelCase table name}

[Maxvien]

As a JavaScript developer, I really want this feature.

[daniel-xyz]

For most users this customisation probably wouldn’t be needed if Hasura would transform all table/column/relation names to GraphQL conventions automatically the same way that Postgraphile does it: https://www.graphile.org/postgraphile/inflection/

On one hand it’s nice that you can rename all fields by yourself, but on the other it is frustrating that you’re still stuck to the GraphQL type names that Hasura generates from tacked tables. For example, I now have camelCase fields but snake_case types and can’t find any option to rename those types apart from defining new custom types.

The whole customization shouldn’t even be necessary in the first place. I think it’s a “nice to have”, but more importantly, Hasura should apply common GraphQL conventions automatically or via a checkbox when you’re about to track new tables. This is something that I, as a new user, miss by far the most after a few days playing around with Hasura.