WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
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 path is split on dots and resolved step by step: `user.address.city`.
1050
+
- Missing or `null` nested values are pushed to the bottom for ascending order (and top for descending) because `null/undefined` are treated as greater than defined values in asc ordering.
1051
+
- Works the same for client-side sorting and for server-side loaders: when using an async loader the same `sortField` (e.g. `user.address.city`) is passed so you can implement equivalent ordering on the backend.
1052
+
- Date objects at nested paths are detected and compared chronologically.
1053
+
- Numeric comparison is stable for mixed numeric strings via Intl.Collator with numeric option.
1054
+
1055
+
Edge cases to consider in your own data:
1056
+
- Deeply missing branches like `user.profile.settings.locale` simply result in `undefined` and will follow the null ordering logic above.
1057
+
- Arrays are not traversed; if you need array-specific sorting you should pre-normalize data into scalar fields before passing to the table.
1058
+
1027
1059
### Server-side sorting
1028
1060
1029
1061
When you provide an async function to `data`, the table will pass the current sort along with pagination params.
0 commit comments