Table sorting needs clarification/revisement
Describe the enhancement or change From the 9/16/2024 design share session, sorting was a topic mentioned, including how "favorites" sorting should work (since typically there's no text to sort by, only an icon).
I gave my initial thoughts on this in the design share, mentioning that if you view it in a sort of alphabetical order, "Favorited" comes before "Unfavorited"/"Not favorited", so following that logic an ascending sort order (with the arrow UP icon) should sort rows so that favorited rows are first (right now our favoritable example does the opposite). Of course this logic kind of breaks depending on the verbiage you're using: "Starred" comes alphabetically after "Not starred". Perhaps if we view it more as an 'active" and "inactive" state universally that logic would fit in all situations, though.
What we should do:
- Investigate how "favorited" rows should be sorted based on the sort type and what icon should be used; we should see if there's a common pattern for this elsewhere, then from there we may need to update logic in our code.
- Depending on the outcome of the above, we should make sure we make applicable updates in the core repo as well as update any design guidelines
Is this request originating from a Red Hat product team? If so, which ones and is there any sort of deadline for this enhancement?
Any other information?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
cc @andrew-ronaldson @lboehling @kaylachumley do y'all have any thoughts on the sort order of non-text based ("favorited", "checked", etc) columns?
I like the active/inactive option where the user made a choice to favourtive/star, check, etc. and those should be sorted to the top first. active inactive will work for the alpha sorting too
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.