-
Notifications
You must be signed in to change notification settings - Fork 2.8k
console: select first operator by default (close #5729) #5730
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: select first operator by default (close #5729) #5730
Conversation
|
Beep boop! 🤖 Hey @bertyhell, thanks for your PR! One of my human friends will review this PR and get back to you as soon as possible. Stay awesome! 😎 |
rikinsk
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.
Hey @bertyhell. Thanks a ton for raising this PR. We really appreciate it.
Unfortunately the solution implemented here does not work as expected. The operator dropdown is a controlled element and the selected value comes from the redux state. hence just displaying the first element as selected will not actually set the operator in the state and when the Run Query button is hit the filter will not actually be applied. The actual solution might involve setting the appropriate state and shouldnt need any changes to the UI components.
|
Beep boop! 🤖 Hey @bertyhell! Sorry that your PR wasn’t merged. Do take a look at any of the other open issues to see if you’d like to take something up! We’re around on Discord if you have any questions 😄 |
Description
When filtering rows in the data tab in the hasura console, the first operator will be selected by default.
Changelog
CHANGELOG.mdis updated with user-facing content relevant to this PR. If no changelog is required, then add theno-changelog-requiredlabel.not yet, I'm not sure under which version I need to add this.
Affected components
Related Issues
#5729
Solution and Design
Steps to test and verify
Catalog upgrade
Does this PR change Hasura Catalog version?
Metadata
Does this PR add a new Metadata feature?
GraphQL
Breaking changes