Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introspector should allow customisation for node and relationship names #4075

Open
moghammed opened this issue Oct 6, 2023 · 0 comments · May be fixed by #4076
Open

Introspector should allow customisation for node and relationship names #4075

moghammed opened this issue Oct 6, 2023 · 0 comments · May be fixed by #4076
Labels
feature request New feature or request

Comments

@moghammed
Copy link

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:

  1. Every node type is called Resource##
  2. 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.

@moghammed moghammed added the feature request New feature or request label Oct 6, 2023
@moghammed moghammed linked a pull request Oct 6, 2023 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant