Fix case-sensitive sorting of filter values in Issues page (Vibe Kanban) #5
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
The filter dropdowns (Repository, Evaluator) in the Issues page were sorting values using JavaScript's default
.sort(), which performs case-sensitive comparison. This caused uppercase entries (e.g., "PostHog/posthog") to appear before lowercase ones (e.g., "bigint/hey"), resulting in an unintuitive ordering for users.Changes
src/api/routes/issues.ts.sort()with.sort((a, b) => a.localeCompare(b, undefined, { sensitivity: "base" }))for bothevaluatorsandrepositoriesfilter arraysWhy
The previous case-sensitive sort grouped all uppercase-starting names before lowercase ones, making it harder for users to find repositories and evaluators in the filter dropdowns. Case-insensitive sorting matches user expectations for alphabetical lists.
Implementation details
localeComparewithsensitivity: "base"which ignores both case and diacritics for sortingThis PR was written using Vibe Kanban