Tool only works if your naming in Neo4j matches your naming in your graphQL schema

[grantvermeer]

After discussing this issue with @jexp, he came up with the idea of adding support for mapping functions to be passed in that would map a graphQL name to a neo4j name. The brainstormed idea has 4 mapping functions, 1 for each: labels, rel-types, node-props, rel-props.

For the properties mapping functions, it would be ideal to have it dependent on the parent type (aka node/relationship label), otherwise the property of name on the movie type would always be remapped in the same was as the property of name on the user type.

[purplemana]

@grantvermeer Has there been any progress on this?

[grantvermeer]

@purplemana We actually ended up finding it easier to write our own graphQL -> cypher converter because of some of the complications with our naming schema.

[michaeldgraham]

https://github.com/neo4j-graphql/neo4j-graphql-js/issues/608