Fix cancellation logic in Picker onDidChangeValue handler (fixes #247945) #247946
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.
The onDidChangeValue in the quick access picker has logic to cancel the previous search as the user is typing.
However this logic was never actually called because the
value
setter onDisposableStore
calleddispose()
on the previous value. The problem is that callingdispose()
withoutcancel()
just removes all the listeners without triggering their cancellation handlers. So thedispose(true)
runs but it's a no-op; there's nothing left to cancel.This PR fixes the issue by running the cancellation first, then updating the
DisposableStore
value.I observe a 2-10x faster experience when typing in a fairly large workspace, depending on the exact search term.
Resolves #247945