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
that the multiplePriority is only considered when sorting entries client-side. If one however wants to use sorting on the server-side one has no way to access the multiplePriority and therefore has to implement sort priority manually.
Some users might already rely on the current behaviour. I therefore would recommend to make sorting by multiplePriority as well as multipleMode a feature that can be turned on or off and use different defaults for client- and server-side sorting.
The text was updated successfully, but these errors were encountered:
Reproduction link
Steps to reproduce
Click on Text to sort ascending after that click on Number to sort ascending.
What is expected?
Since Number has a higher multiplePriority than Text the order of the SorterResults should be: Number, Text
What is actually happening?
The SorterResults is based on the order of clicking the columns not on the multiplePriority.
It is clear from the current implementaion:
ant-design/components/table/hooks/useSorter.tsx
Lines 246 to 253 in 7f50e3f
that the multiplePriority is only considered when sorting entries client-side. If one however wants to use sorting on the server-side one has no way to access the multiplePriority and therefore has to implement sort priority manually.
Some users might already rely on the current behaviour. I therefore would recommend to make sorting by multiplePriority as well as multipleMode a feature that can be turned on or off and use different defaults for client- and server-side sorting.
The text was updated successfully, but these errors were encountered: