-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
customising graphql typename generation per source #6974
Comments
Another vote for this feature, or more largely described as namespacing sources. Multiple sources is a key part of the Hasura story and adding a configurable guard for field collisions would be useful! |
@dmoverton A source offers some schema customization options under |
@0x777 the |
Ah, right. Sorry, my bad. You can ignore my previous message. |
Closing this issue, as the PR has been merged. |
What was the PR that solved this issue? Could you point to the version it was released? Thanks |
Currently a source's name is not used in the GraphQL types that we generate. So if two sources have same table names, they can't both be tracked because of type and field conflicts. One can work around this to some extent by customizing each of the table names that cause the conflict. However, it would be very convenient to have this configured per source. We add
customization
field to the*_add_source
API with the following spec:The text was updated successfully, but these errors were encountered: