-
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
console: allow customising exposed column names of views (close #3689) #4255
Conversation
Review app for commit b1d3fa1 deployed to Heroku: https://hge-ci-pull-4255.herokuapp.com |
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.
Changelog approved
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.
UX approved
Review app for commit 930d0f4 deployed to Heroku: https://hge-ci-pull-4255.herokuapp.com |
Deploy preview for hasura-docs ready! Built with commit 3f2e8a1 |
Review app for commit 3f2e8a1 deployed to Heroku: https://hge-ci-pull-4255.herokuapp.com |
Review app for commit 4236ba5 deployed to Heroku: https://hge-ci-pull-4255.herokuapp.com |
Review app https://hge-ci-pull-4255.herokuapp.com is deleted |
Description
Currently, the UI does not allow customising the GraphQL field names for columns of views. This PR implements that.
Changelog
CHANGELOG.md
is updated with user-facing content relevant to this PR.Affected components
Related Issues
#3689
Steps to test and verify
Try editing the GraphQL field names of view columns.