test: Add test case for exact match prioritization in fzf

[JonasBa]

Summary

Adds test cases to demonstrate and document the expected behavior for exact match prioritization in the fzf fuzzy search algorithm, both at the algorithm level and at the CompactSelect component level.

Test Cases

1. Unit Test (fzf.spec.tsx)

Tests the fzf algorithm directly with the pattern "path" against:

• binary_path
• code.file.path
• path

Verifies that the exact match scores higher than partial matches.

2. Integration Test (compactSelect.spec.tsx)

Tests CompactSelect with search enabled using the same real-world examples from the Slack discussion. Verifies that when searching for "path", the exact match option appears first in the sorted results.

Current Behavior

Both tests are currently skipped to avoid blocking CI. When unskipped locally, they fail because all three options receive the same score (104), confirming the issue described in the Slack thread about exact matches not being boosted properly.

Next Steps

Once the fix from #110680 is applied, these tests should be unskipped and will serve as regression tests to ensure exact matches are properly prioritized at both the algorithm and component levels.

Related

• Related to fix(compact-select): Boost exact matches in default search matcher #110680

Slack Thread

  

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Exact match detection condition is too broad
  • Replaced the condition with 'textLength === patternLength' which correctly identifies exact matches when combined with the subsequence match.

Or push these changes by commenting:

@cursor push b39408e01b

Preview (b39408e01b)

diff --git a/static/app/utils/search/fzf.tsx b/static/app/utils/search/fzf.tsx
--- a/static/app/utils/search/fzf.tsx
+++ b/static/app/utils/search/fzf.tsx
@@ -137,7 +137,7 @@
   let [score, matches] = calculateScore(text, pattern, sidx, eidx, caseSensitive);
 
   // Boost exact matches (text === pattern) so they rank above partial matches
-  if (sidx === 0 && eidx === textLength) {
+  if (textLength === patternLength) {
     score += scoreMatch;
   }

_{This Bugbot Autofix run was free. To enable autofix for future PRs, go to the Cursor dashboard.}

[JonasBa]

@cursoragent fix the following lint error

/home/runner/work/sentry/sentry/static/app/utils/search/fzf.tsx
Error:   137:15  error  'matches' is never reassigned. Use 'const' instead  prefer-const

[cursor]

Fixed! I've resolved the lint error by separating the destructuring:

• Changed let [score, matches] = calculateScore(...) to use const for the destructuring
• Introduced a scoreBase variable that holds the initial score
• Declared score separately as let since it needs to be reassigned for the exact match boost

The matches variable is now properly declared as const since it's never reassigned, while score remains as let for the exact match boosting logic. Tests pass and pre-commit checks pass.