-
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
[wip] actions with graphql tx over websockets #3561
Conversation
…nerating definition list
Deploy preview for hasura-docs ready! Built with commit 28d7fa1 |
Review app for commit 9462484 deployed to Heroku: https://hge-ci-pull-3561.herokuapp.com |
Review app for commit 98b2889 deployed to Heroku: https://hge-ci-pull-3561.herokuapp.com |
98b2889
to
cdfb4a9
Compare
Review app for commit 28d7fa1 deployed to Heroku: https://hge-ci-pull-3561.herokuapp.com |
Review app https://hge-ci-pull-3561.herokuapp.com is deleted |
This is only for preview testing, not intended to merge.
Refer #3557 for graphql transactions over websockets.
Description
Affected components
Related Issues
Solution and Design
Server checklist
Catalog upgrade
Does this PR change Hasura Catalog version?
Metadata
Does this PR add a new Metadata feature?
run_sql
auto manages the new metadata through schema diffing?run_sql
auto manages the definitions of metadata on renaming?export_metadata
/replace_metadata
supports the new metadata added?GraphQL
Breaking changes
No Breaking changes
There are breaking changes:
Metadata API
Existing
query
types:args
payload which is not backward compatibleJSON
schemaGraphQL API
Schema Generation:
NamedType
Schema Resolve:-
null
value for any input fieldsLogging
JSON
schema has changedtype
names have changedSteps to test and verify
Limitations, known bugs & workarounds