We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I.e. this will not return any result
mutation { set { <1> <text> "This is a colour"@en-us . } } { q(func: uid(1)) { text@en-us } }
But this will return result correctly
mutation { set { <1> <text> "This is a colour"@en . } } { q(func: uid(1)) { text@en } }
Looks like gql parser has some issues to parse language tag with '-' in the middle.
The text was updated successfully, but these errors were encountered:
I've add a hack in #1428, which allows queries to use underscores, i.e. "en_us", while mutations and RDF are still using "-".
Sorry, something went wrong.
Fix for #1427
cc59210
ce013bd
1. Auto delete schema for predicate on deletion of predicate if it wa…
d47f51b
…s set implicitly. 2. Run query without debug flag when user clicks on JSON. 3. Fix #1427 and #1444.
pawanrawal
No branches or pull requests
I.e. this will not return any result
But this will return result correctly
Looks like gql parser has some issues to parse language tag with '-' in the middle.
The text was updated successfully, but these errors were encountered: