-
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
misc console improvements #3435
Conversation
Deploy preview for hasura-docs ready! Built with commit 7fece8a |
Review app for commit 36cbb69 deployed to Heroku: https://hge-ci-pull-3435.herokuapp.com |
Review app for commit f344387 deployed to Heroku: https://hge-ci-pull-3435.herokuapp.com |
Review app for commit b714990 deployed to Heroku: https://hge-ci-pull-3435.herokuapp.com |
Conflicts: console/src/components/Services/Data/Schema/Schema.js console/src/components/Services/Data/TableRelationships/RelationshipEditor.js
Review app for commit 0408a05 deployed to Heroku: https://hge-ci-pull-3435.herokuapp.com |
Review app for commit dc7092d deployed to Heroku: https://hge-ci-pull-3435.herokuapp.com |
Review app for commit 40ea0a9 deployed to Heroku: https://hge-ci-pull-3435.herokuapp.com |
Review app for commit 7fece8a deployed to Heroku: https://hge-ci-pull-3435.herokuapp.com |
Review app https://hge-ci-pull-3435.herokuapp.com is deleted |
* persist rawSql content to LS * handle cleanup of admin secret related persisted info if admin secret is removed * show gql compatibility warning for invalid schemas and add to tooltip that types depending on the identifier will not be exposed over GraphQL * display non trackable functions section even if there are no functions * increase width of stack trace container on error page * fix PG version fetch query
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