You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The sortDirection behavior only affects the final column sorted, as multiple columns cannot be sorted simultaneously, since this would require reordering individual cell data among rows, thus scrambling the table data. However, it is unclear what is happening from a UI perspective, as it shows both arrows.
What should probably occur is that only the final arrow should show, and there should be a console warning that multiple columns have been set to be sorted.
The text was updated successfully, but these errors were encountered:
The table allows you to select multiple columns by holding Shift and clicking the column. It's pretty useful. Example use case: Sort a table by the Last Name column, and then secondary sort on the First Name column.
Hm, not sure I understand how a secondary sort would work since it must necessarily change the sort order from the first time around. The only time I can think of where it would matter is if there are multiple entries that are the same on the initial sort. But I'm not sure how to make it clear which sort direction should receive priority. If you can think of a decent API and UX for that feel free to open a new issue with a detailed explanation, and it can be treated as a new feature. This issue is specifically to solve some confusing UI around the current functionality.
The
sortDirection
behavior only affects the final column sorted, as multiple columns cannot be sorted simultaneously, since this would require reordering individual cell data among rows, thus scrambling the table data. However, it is unclear what is happening from a UI perspective, as it shows both arrows.What should probably occur is that only the final arrow should show, and there should be a console warning that multiple columns have been set to be sorted.
The text was updated successfully, but these errors were encountered: