-
Notifications
You must be signed in to change notification settings - Fork 226
Use native VS Code test UI on canary #2306
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
e1dae0b
Avoid identifier collision with new VS Code version
4804220
Use native VS Code test UI in canary
7ea7d6c
Merge remote-tracking branch 'origin/main' into dbartol/new-test-ui
e986b07
Add missing mock method after `@types/vscode` upgrade
397b585
Fix test adapter tests
cb93c84
Test tests
eca8cce
Update extensions/ql-vscode/src/test-manager.ts
c963cf6
Merge branch 'main' into dbartol/new-test-ui
8f29e1c
Add separate command for "Accept Output" on test item context menu
c9507df
Merge branch 'dbartol/update-vscode-types' into dbartol/new-test-ui
da3f482
Reconsider the fanciness of CodeQL tests
8f5f43f
Merge branch 'main' into dbartol/new-test-ui
8c2c25e
Fix PR feedback
a52391b
Merge branch 'dbartol/new-test-ui' of https://github.com/github/vscod…
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 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
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
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
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
Oops, something went wrong.
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.
As much as possible, we try to dis/enable all canary features without a restart. It looks like this is not following the pattern. I don't know how easy it would be to do, though.
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.
Hmm. There's no way to "unregister" a
TestControllerAFAICT, but maybe just deleting all of itsTestItems would be equivalent. I'll have to see if there's a way to unregister the legacy test adapter, but it might not be worth the effort.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.
OK, there is a way to unregister the legacy test stuff. However, handling of the commands we expose is trickier. We share the same command IDs between the two implementations, but they route to slightly different implementations depending on which test UI we're using.
Given how easy the transition to the new UI was, and how annoying our dependency on that third-party extension is, I suspect we'll move this out of canary pretty soon anyway.
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.
If it's going to take significant time and still be imperfect, I don't think it's worth taking on for a transitional feature.