Clean up localeCompare usage for proper internationalization (fixes #3888) #14087
+62
−30
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Standardizes usage of the
localeComparewrapper fromi18n.jsacross all sorting operations to ensure proper locale-aware string comparison.Changes:
localeComparewrapper in i18n.js to default tocurrentLanguageandusage: 'sort'.localeCompare()callscompareLanguages()to use proper locale-aware comparisonScreenshots showing sorted lists work correctly:
References
Fixes #3888
Reviewer guidance
The changes are mechanical - replacing direct
.localeCompare()calls with the centralized wrapper. No risky areas (no auth, migrations, or API changes).To verify: sorting of user/class lists should work correctly for names with accented characters and non-Latin scripts.