Version Information
Server Version: 2.16
Environment
OSS
What is the current behaviour?
When the naming convention is set to default graphql, it is not possible to override a field name.
The column access_token is exposed via graphql as accessToken.
When the name is overriden in the UI, the option is ignored

Resulting schema

What is the expected behaviour?
If the field name is set, the option should be respected.
It should be possible to still expose certain fields with underscores in the name.