-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
GraphQL Schema Not support <> using @dgraph(pred: "<other language>") #5296
Comments
Angular brackets are exclusive for Cheers. |
@draph(pred: "***") dont't support other language if don't use "<>" |
Sorry, but what do you mean by support other language? the edge is UID type. There's no language support for UID, only Strings. |
Oh, you mean i18n in predicates. Not sure if GraphQL specs support i18n. I gonna check. PS. You used the "FROM", you should use a nonlatin example to make it obvious. |
I wasn't able to find anything about i18n predicates in https://spec.graphql.org/ @MichaelJCompton is there support for languages in predicates in GraphQL? |
https://graphql.dgraph.io/docs/dgraph/
Because GraphQL Spec requires that type and field (predicate) names are generated from /[_A-Za-z][_0-9A-Za-z]/. |
Hi, This should work to allow you to map GraphQL compliant names down to names in other languages. I'll arrange this to be looked at in our next sprint and we'll patch it for 20.03.2 and master. |
Using graphql to update schema with @dgarph would not work while muation
Dgraph Schema would generate a "" predicate ,but there should not be "<>" in real schema data
The text was updated successfully, but these errors were encountered: