This repository has been archived by the owner on Sep 6, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Fixes #2608 (Quick Open shows red on first use) #3184
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
e423527
Fixes #2608 (QuickOpen shows red on first use) and also makes QuickOp…
dangoor a34d98c
Reset StringMatcher caches when file list is retrieved.
dangoor 7641f18
Addresses review feedback from @peterflynn.
dangoor 9384b87
Eliminates "red" Quick Open field while waiting for initial index build
dangoor f419483
addMatchers needs to be in a beforeEach or a test.
dangoor File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So if I understand this right, nothing will actually refresh the results list once the new index has been built... but the next time the user changes the query text, even within the same Quick Open session, the results will start reflecting the new index?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also... do we need both this _filenameMatcher.reset() and matcher.reset() above? I think they will always be the same object.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, you're right that there's no automatic refresh until the user changes the query string. You're also right that only one call to
.reset()
is needed.Do you think it's worthwhile to force a refresh when the file list updates? It's not immediately obvious to me how we'd do that, but I'm guessing there's got to be a way we can prod the smartautocomplete widget into acting as if the query changed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, I don't think we need to bother with a forced refresh... just wanted to make sure I understood the intent of the code.