-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
9012-registerTerminalLinkProvider-stub: for vscode-java-debug #9048
9012-registerTerminalLinkProvider-stub: for vscode-java-debug #9048
Conversation
Since this PR contains code copied from VSCode, it may require a CQ, so you may want to get that process started. |
I checked and this copied code was requested in approved CQ https://dev.eclipse.org/ipzilla/show_bug.cgi?id=22677 |
Great! So you read that CQ as permitting copying from VSCode 1.51.0 quite broadly, then? If so, that's very nice, and we should update our wiki entry about copying code from VSCode accordingly. |
@colin-grant-work |
Based on comment by @marcdumais-work in another thread I assume that old CQ that contain the copied code is enough: |
To be clear, it's not enough that there exist a CQ for the same vscode version, the CQ attachment has to contain the copied code, verbatim - i.e. all files we copied-from have to be present (we can then modify our version of what we copied, of course). If we have several CQs per vscode release, we could discuss if it makes sense for the Foundation to analyse vscode versions as they come-out, wholly and preemptively. Then we would not need a CQ if we copy from a pre-approved version.
👍 |
…-java-debug extension added registerTerminalLinkProvider stub which is invoked upon extension activation Signed-off-by: Dan Arad <[email protected]>
33af8ac
to
110afa5
Compare
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.
The stub seems fine and it was copied from code covered in the previous CQ:
Signed-off-by: Dan Arad [email protected]
Added registerTerminalLinkProvider stub which is invoked upon extension activation.
What it does
Fixes first problem of #9012:
vscode-java-debug invokes vscode.window.registerTerminalLinkProvider upon extension activation. This method was not implemented in Theia - added stubs.
For second problem see #9049
How to test
Approved CQ (existing already) covering theia.d.ts copied code: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=22677
Note:
for better behavior change this user setting to "internalConsole" (instead of "integratedTerminal"):
"java.debug.settings.console": "internalConsole"
Review checklist
Reminder for reviewers