Version Information

Server Version: 2.11.1

Environment

OSS

What is the current behaviour?

The naming convention seems to be inconsistent in the following way:

1. mutation_root
2. query_root
3. subscription_root
5. Constraint name:

enum UserConstraint {
  user_pkey
}

6. update_columns

input UserOnConflict {
  constraint: UserConstraint!
  update_columns: [UserUpdateColumn!]! = []
  where: UserBoolExp
}

4. pk_columns

updateUserByPk(
    _set: UserSetInput
    pk_columns: UserPkColumnsInput!
  ): User

7. affected_rows

8. Aggregates

stddev_pop
stddev_samp
var_pop
var_samp

9. JSON

_delete_at_path
_delete_elem
_delete_key

10. comments
The following have already been fixed in the schema itself but still appear in comments

on_conflict
order_by

All the above don't match the graphql-default expected bahaviour

What is the expected behaviour?

The graphql-default naming convention should be respected

How to reproduce the issue?

1. Set naming convention to graphql-default.
2. Add a table called user and add a JSONB field to it
3. Check the schema for type names and field names.