-
Notifications
You must be signed in to change notification settings - Fork 12
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
DM-11457: Selected table rows should be kept after sorting #545
Conversation
IRSA-1434: Handle 'null' sort order.
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.
I've built IRSAViewer and when i do a filter / sort with rows selected (not all) it doesn't seems to respect the rows selected. I was expecting that if i select a row and filter or sort, the same row stays selected if the filter is positive or if sorted the row should 'move' and kept the selection, i don't see that in my local.
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.
It works as described in both firefly and irsaviewer. I tried sorting and filtering from table, chart, and image plot. The rows selected in the previous iteration stay selected.
- fix SelectInfo's rowCount not updated to reflect current table.
@ejoliet, I've just pushed a commit to fix the problem you saw in irsaviewer. It was a bug in table support. However, it was masked by plot.ly chart's code. That's why it was not noticeable in firefly and only in irsaviewer. Please check again. |
Here are some cases I found,
|
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.
Last push fixes what i've seen in irsaviewer. Good to go.
It's a bug. I've fixed it. |
https://jira.lsstcorp.org/browse/DM-11457
As described in the ticket, selection info should be kept after sorting and filtering.
In the case of filtering, when a selected row is removed due to a filter, it will be removed from selection info as well. This is to ensure that the selection info is valid for the current view.
For example:
Also in this ticket,
null
values are sorted to top for ascending and to the bottom on descending.This ticket can be tested on any table.