-
Notifications
You must be signed in to change notification settings - Fork 2.8k
console read only mode #3466
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
console read only mode #3466
Conversation
|
Deploy preview for hasura-docs ready! Built with commit 9812306 |
|
Review app for commit 34c7d3d deployed to Heroku: https://hge-ci-pull-3466.herokuapp.com |
|
Review app for commit 2d97167 deployed to Heroku: https://hge-ci-pull-3466.herokuapp.com |
|
Review app for commit 58ea11a deployed to Heroku: https://hge-ci-pull-3466.herokuapp.com |
|
Review app for commit a371141 deployed to Heroku: https://hge-ci-pull-3466.herokuapp.com |
wawhal
left a comment
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.
Code LGTM
|
Review app https://hge-ci-pull-3466.herokuapp.com is deleted |
|
Review app for commit 9812306 deployed to Heroku: https://hge-ci-pull-3466.herokuapp.com |
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_sqlauto manages the new metadata through schema diffing?run_sqlauto manages the definitions of metadata on renaming?export_metadata/replace_metadatasupports the new metadata added?GraphQL
Breaking changes
No Breaking changes
There are breaking changes:
Metadata API
Existing
querytypes:argspayload which is not backward compatibleJSONschemaGraphQL API
Schema Generation:
NamedTypeSchema Resolve:-
nullvalue for any input fieldsLogging
JSONschema has changedtypenames have changedSteps to test and verify
Limitations, known bugs & workarounds