You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I'm building a GraphQL api for a neo4j database that I don't control. The database schema is likely to keep changing for a while, as it is still under construction. The database contains a knowledge graph, in which all nodes have the label "Resource", and additional more descriptive labels that are prefixed with the source of the data they contain. This causes 2 problems when translated to a GraphQL schema:
Every node type is called Resource##
The prefixes make the GraphQL api rather cumbersome to work with
Describe the solution you'd like
I would like a way to choose which type name will be used for a node, and to choose what the field name for relations will be in the schema.
Describe alternatives you've considered
I've considered replacing the names after the schema is created, but this is much more error prone than choosing the right names while formatting, when all the needed information is still readily available.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I'm building a GraphQL api for a neo4j database that I don't control. The database schema is likely to keep changing for a while, as it is still under construction. The database contains a knowledge graph, in which all nodes have the label "Resource", and additional more descriptive labels that are prefixed with the source of the data they contain. This causes 2 problems when translated to a GraphQL schema:
Describe the solution you'd like
I would like a way to choose which type name will be used for a node, and to choose what the field name for relations will be in the schema.
Describe alternatives you've considered
I've considered replacing the names after the schema is created, but this is much more error prone than choosing the right names while formatting, when all the needed information is still readily available.
The text was updated successfully, but these errors were encountered: