-
Notifications
You must be signed in to change notification settings - Fork 797
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
Add graphql support #3266
base: main
Are you sure you want to change the base?
Add graphql support #3266
Conversation
…y/surrealdb into add-graphql-support
Great to see some movement on this, might be minor; |
pub from: Option<Kind>, | ||
pub to: Option<Kind>, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we internally keep calling these in
and out
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The issue with that is in is a keyword so you'd have to do #in
…d-define-relation
Co-authored-by: Mees Delzenne <DelSkayn@users.noreply.github.com>
…y/surrealdb into add-define-relation
Thank you for submitting this pull request! We appreciate you spending the time to work on these changes.
What is the motivation?
GraphQL is a useful tool with a large ecosystem surrounding it, allowing SurrealDB to integrate with that will ease adoption and increase use cases.
What does this change do?
This pr adds a new /gql endpoint, which allows proves an autogenerated schema, as well as allowing custom functions to be exposed, then parses, validates and executes graphql queries.
What is your testing strategy?
Testing not currently implemented.
Is this related to any issues?
Closes #2379.
Does this change need documentation?
Have you read the Contributing Guidelines?