Currently, the SchemaBuilderSchemaOptions.FieldNamer is defined simply as Func<string, string>. So it converts field names for the entire GQL schema (using camel case by default), including introspection.

In our project we would like to use PascalCase for our data model leaving introspection schema und queries using the default naming convention (camel case), as most of the GQL-Tools rely on it.

Possible solutions:

1. make SchemaBuilderSchemaOptions.FieldNamer only affect the entity model and always use DefaultFieldNamer for introspection (breaking change?)
2. introduce a separate FieldNamer for introspection
3. provide more context to FieldNamer function (as a new optional parameter) to possibly choose an appropriate convention depending on the use case