-
Notifications
You must be signed in to change notification settings - Fork 14k
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
fix(explore): make SORT DESCENDING visible if SORT BY has value #17726
Conversation
Codecov Report
@@ Coverage Diff @@
## master #17726 +/- ##
==========================================
- Coverage 67.79% 67.77% -0.02%
==========================================
Files 1605 1605
Lines 64207 64224 +17
Branches 6790 6791 +1
==========================================
+ Hits 43529 43530 +1
- Misses 18822 18838 +16
Partials 1856 1856
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
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.
So if SORT BY is set, does it sort descending by default?
Right. |
Removed 1.4.2 label as this cherry requires monorepo which isn't available on the 1.4 branch |
why exist default sort(sort by x-field) this maybe cause The Chart Result data difference to sqlab query result |
SUMMARY
enhancement: Currently, if
SORT BY
is not set,SORT DESCENDING
is not effective, for this reason, it will mislead the user, here we change it to show this control only if sort by is set.BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
after
TESTING INSTRUCTIONS
ADDITIONAL INFORMATION