-
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
register vscode.openWith api #9881
register vscode.openWith api #9881
Conversation
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.
Hi @amos42 and thank your for your contribution.
Please be sure to sign the eclipse contributor agreement (eca) with the same email as your authorship in order for us to accept the changes.
Also, the testing steps are quite non descriptive. However, the referenced issue mentions a perfectly viable way of testing your changes. Would you mind replacing your testing steps simply with "See #9865 for reproduction steps"?
Also, please don't modify the "Review checklist" and the "Reminder for reviewers" from the PR template. Instead, could you please reinstate them and mark the checklist as resolved using [x]
?
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.
I noticed that the custom-editor-example
provided by vscode does not correctly work with the current version of Theia, due to Theia not creating the file when executing the command. Which is quite weird, since the command does not specify to create a new file. It just creates an URI and passes this URI into the opener command.
I was able to trick Theia into displaying the editor either way. So I guess I can confirm that the changes are working correctly. How did you test your changes?
packages/plugin-ext-vscode/src/browser/plugin-vscode-commands-contribution.ts
Outdated
Show resolved
Hide resolved
packages/plugin-ext-vscode/src/browser/plugin-vscode-commands-contribution.ts
Outdated
Show resolved
Hide resolved
packages/plugin-ext-vscode/src/browser/plugin-vscode-commands-contribution.ts
Outdated
Show resolved
Hide resolved
packages/plugin-ext-vscode/src/browser/plugin-vscode-commands-contribution.ts
Outdated
Show resolved
Hide resolved
packages/plugin-ext-vscode/src/browser/plugin-vscode-commands-contribution.ts
Outdated
Show resolved
Hide resolved
packages/plugin-ext-vscode/src/browser/plugin-vscode-commands-contribution.ts
Outdated
Show resolved
Hide resolved
packages/plugin-ext-vscode/src/browser/plugin-vscode-commands-contribution.ts
Outdated
Show resolved
Hide resolved
packages/plugin-ext-vscode/src/browser/plugin-vscode-commands-contribution.ts
Outdated
Show resolved
Hide resolved
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.
Reminder that you still haven't signed the eclipse contributor agreement (eca) with the same email as your authorship in order for us to accept the changes.
|
@amos42 You used different emails in your commits, that's probably the reason the eca check is still failing. (once |
Ok. I will fix it according to your advice. |
54e434b
to
08227d6
Compare
Signed-off-by: Ju, Gyeong-min <jcmh74@gmail.com>
08227d6
to
6632ce5
Compare
I've included a simple example in the description for reviewers. |
I build a running example extension for other reviewers: download You still need to create a file like this: |
packages/plugin-ext-vscode/src/browser/plugin-vscode-commands-contribution.ts
Show resolved
Hide resolved
packages/plugin-ext-vscode/src/browser/plugin-vscode-commands-contribution.ts
Outdated
Show resolved
Hide resolved
packages/plugin-ext-vscode/src/browser/plugin-vscode-commands-contribution.ts
Outdated
Show resolved
Hide resolved
Signed-off-by: Ju, Gyeong-min <jcmh74@gmail.com>
993e507
to
2bb2833
Compare
packages/plugin-ext-vscode/src/browser/plugin-vscode-commands-contribution.ts
Outdated
Show resolved
Hide resolved
Signed-off-by: Ju, Gyeong-min <jcmh74@gmail.com>
Signed-off-by: Ju, Gyeong-min <jcmh74@gmail.com>
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.
Thank you for your contribution @amos42, the changes look good to me and I can confirm that the vscode.openWith
command works as expected.
Signed-off-by: Ju, Gyeong-min <jcmh74@gmail.com>
Signed-off-by: Ju, Gyeong-min <jcmh74@gmail.com>
register vscode.openWith api
What it does
Fixes #9865
Register vscode.openWith api
VSCode provides both 'open' and 'openWith' commands.
However, theia does not provide the 'openWith' command.
The 'open' command is a command that automatically finds and opens an editor that matches the 'resource' parameter.
'openWith' allows us to directly designate the editor we want and open it.
How to test
You can create a VSCode plugin and test it using the following code.
.
.
.
Here is the code for testing.
Sample plug-ins code for test
Review checklist
Reminder for reviewers