-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Custom GraphQL types for tables not conforming to GraphQL naming spec #3811
Comments
The API that you use is for fields but the type (of the table) needs to be changed as well. Changing the title of this issue to reflect the same. |
When a new table type is given, then all the corresponding fields should change to the new name like |
See the new spec in comment below by 0x777 Old Spec (previously in #4821) : For postgres, we already have a This can include
This should be possible via
|
When we track a table, the table name becomes the root for every field name and type name that is generated, for example 1. Table IdentifierLet's introduce a new optional top level field under This will help these two use cases:
2. Custom Type NamesWe currently do not allow customising the names of generated types. Let's add a new option,
3. Introduce
|
…uthenticated context. ### Description This very small PR fixes an error introduced in #3811, when changing the collision detection code: we were properly doing collision detection for remote schemas for the unauthenticated context, and also removing remote relationships... but then we were not using the result to build the schema. PR-URL: hasura/graphql-engine-mono#3986 GitOrigin-RevId: 26a5553bf82574f2764fd594b0616dfea95a4757
Version: 1.1.0-beta.2
I have a table from an underlying, existing database that is a legacy table with spaces in the name. Let's call it "User Accounts". This name does not conform to the GraphQL naming standard and thus cannot be exposed over the API.
In an attempt to solve this issue - I went to Modify -> Custom GraphQL Root Fields and , under the Query and Subscription section made the Select "UserAccounts" and hit save. The message said it was successful but I am not seeing "UserAccounts" anywhere under my available Schemas on the GraphIQL page.
The docs say this is available as of version v1.0.0-beta.8 and higher but I am using 1.1.0-beta.2 and it doesn't appear to be working.
The text was updated successfully, but these errors were encountered: