Remove workspaceFolders from app because it turned out not to be useful#2497
Merged
robertbrignull merged 4 commits intomainfrom Jun 12, 2023
Merged
Conversation
charisk
approved these changes
Jun 12, 2023
Contributor
charisk
left a comment
There was a problem hiding this comment.
Thanks for cleaning that up!
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR basically just reverts #2431 and #2437. Since we've decided to use integration tests for the queries panel and not try to push for unit tests it's meant that neither of those changes were particularly useful, or are possibly detrimental.
workspaceFolderswas completely unused, because we have thegetOnDiskWorkspaceFoldersObjectshelper and it made much more sense to call that.onDidChangeWorkspaceFoldersmade little difference, since mocking the VS Code version was just as easy.createEventEmitterwasn't terribly helpful because mocking the VS Code version wasn't hard. It was actually possibly harmful because the default implementation increateMockAppsilently does nothing, which tripped me up when writing tests and my listeners weren't firing. You haven't to know to pass a working emitter constructor when making the mock app, but there's no error that will point you in that direction.This PR will conflict with #2490, but it's not a big problem. I still want to make these changes and I'll fix any conflicts on that PR.
Checklist
ready-for-doc-reviewlabel there.