fix(issues): Keep searched release selected in resolve modal#117496
Conversation
Older releases can be found by exact search, but clearing the search after selection dropped that option from the picker list. CompactSelect still had the value, but no label to render, so it showed None. Keep the selected release available after search clears and add a regression test for the search-only release path. Fixes #117488 Co-authored-by: GPT-5 Codex <noreply@openai.com>
github-actions
Bot
added
the
Scope: Frontend
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 0daee14. Configure here.
| visibleReleases.find(item => item.version === selectedVersion) ?? null; | ||
|
|
||
| setVersion(selectedVersion); | ||
| setSelectedRelease(release); |
There was a problem hiding this comment.
onChange drops selectedRelease lookup
Medium Severity
The options list keeps a search-only release via selectedRelease when the debounced search is empty, but onChange resolves the chosen release only from exactRelease and the current releases fetch. If the user interacts with that option again after another search (or cached exact lookup no longer matches), lookup fails and selectedRelease is cleared while version stays set, so the Version trigger can show None again.
Reviewed by Cursor Bugbot for commit 0daee14. Configure here.
2 participants
Selecting a release that only shows up through exact search made the resolve modal flip back to
Version: None, even though the selected value was still there.Keep the selected release around after search clears so the picker can still render its label, and add a regression test for that path.
Fixes #117488