bindingsand the resulting
resolversare merged and provided to Apollo Server.
typeDefsshows the use of the
@cypherdirective for a computed field, a query, and a mutation type. Any
resolvers, that you provide are not overwritten by the schema augmenting process.
resolverscan be provided if you want to handle the data or be explicit. Otherwise, they will be generated.
typeDefs(required): Your GraphQL type definitions in SDL format
callsConfigures the use of
true): A boolean control that updates the unique property constraints in your Neo4j instance.
true): A boolean control that updates your Neo4j-GraphQL schema.
augmentConfigures the use of
true) A boolean controlling the generation of query types.
true) A boolean controlling the generation of mutation types.
true) A boolean controlling the generation of resolvers for query types.
true) A boolean controlling the generation of resolvers for mutation types.
indexConfigConfigures the management of generated
'cuid') Configures what method to use when generating id field values.
'neo4j'): The key used when storing the created binding into the server's context object.
false): Logs the result of any delegated query or mutation operation,
readOnly(default: false): If you only have read access to a remote server, then you can use this parameter to turn off all processes that assume write access. Mutation types are not generated,
assertcalls are prevented, and
idfields are not generated and managed because we would never be able to write them to the instance. So, this results in forcing the following configuration:
bindingsAn object of bindings where each key is the name for a binding and each value is a configuration object containing the parameters:
readOnly. This can be used to network together a GraphQL binding for multiple remote Neo4j instances with the Neo4j-GraphQL extension installed.