Skip to content

Conversation

@pfalcon
Copy link

@pfalcon pfalcon commented Jan 1, 2026

Previously, this comparison callback was called too late, after applying various adhoc conversions. Chances, they wouldn't work as user want, only leading to confusion. So, as long as the comparison callback is defined, call it as soon, not as late, as possible. This includes letting it decide how null values are sorted, instead of hardcoding a particular behavior. Calling ASAP and skipping all conversions also saves CPU cycles in users' browsers.

Previously, this comparison callback was called too late, after applying
various adhoc conversions. Chances, they wouldn't work as user want,
only leading to confusion. So, as long as the comparison callback is
defined, call it as soon, not as late, as possible. This includes
letting it decide how null values are sorted, instead of hardcoding
a particular behavior. Calling ASAP and skipping all conversions also
saves CPU cycles in users' browsers.
@pfalcon
Copy link
Author

pfalcon commented Jan 1, 2026

Proposed fix for #2653

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant