Proposal allow aliasing fields about graphql

[darrellwarde]

This is going to be more valuable for users of this library with an existing dataset, but want to map the backend property to a different field name on the frontend. These users aren't our current target audience, but I will leave this open as it probably is a feature we should add in the future.

[Andy2003]

@darrellwarde You may have a look at lib_directives.graphql. This is how we define the directives in java. This file (and neo4j_types.graphql) are then loaded into the user provided schema:

https://github.com/neo4j-graphql/neo4j-graphql-java/blob/master/core/src/main/kotlin/org/neo4j/graphql/SchemaBuilder.kt#L225-L237

This is especially helpful since the graphql framework will take care about validating the schema and applying default values.

[danstarns]

@Andy2003 in the current implementation we don't type the directives, as untyped means we can offer greater flexibility IMO*, this is up for discussion internally. If you look at the output schema; no sign of directives. The directive metadata is stored on the Neo4jGraphQL class instead. I do think we should pick up on enum values over strings, in certain places, and so something defo worth looking into.

PS - I think this comment is in the wrong place