Skip to content
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

Add ability to handle vscode.openFolder command #6928

Merged
merged 3 commits into from
Jan 22, 2020
Merged

Add ability to handle vscode.openFolder command #6928

merged 3 commits into from
Jan 22, 2020

Conversation

tomer-epstein
Copy link
Contributor

@tomer-epstein tomer-epstein commented Jan 21, 2020

Signed-off-by: Tomer Epstein [email protected]

Issue: #4050

What it does

This change proposal adds ability to handle vscode.openFolder command.

How to test

  1. git clone https://github.com/tomer-epstein/vscode-open-folder.git
  2. cd vscode-open-folder
  3. npm run compile && npm run pacage
  4. copy vscode-open-folder-0.0.1.vsix to plugins folder
  5. Right click on a folder in the Explorer, choose 'Open Folder New Instance' / 'Open Folder Here' or 'Open Folder Dialog'.

image

Review checklist

Reminder for reviewers

@akosyakov akosyakov added the vscode issues related to VSCode compatibility label Jan 22, 2020
@@ -101,6 +108,20 @@ export class PluginVscodeCommandsContribution implements CommandContribution {
}
});

commands.registerCommand(VscodeCommands.OPEN_FOLDER, {
isVisible: () => false,
execute: async (resource?: URI, options?: WorkspaceInput | undefined) => {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not suer about WorkspaceInput.

We should use VS Code type definition for options and translate it to WorkspaceInput. Could you look up the relevant code in VS Code?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@amiramw
Copy link
Member

amiramw commented Jan 22, 2020

@akosyakov i'm confused with regard to git pod workspace created in this PR. When I login and open chrome dev tools I don't see the changes. Is there something wrong with the CI or I am missing something?

@tomer-epstein
Copy link
Contributor Author

@amiramw , try this:

image

@akosyakov
Copy link
Member

@amiramw When you log in you see Gitpod Theia, not Theia from the PR. There should be a notification to open a Theia from the PR, or you can open it from the port view as @tomer-epstein pointed out

@akosyakov
Copy link
Member

akosyakov commented Jan 22, 2020

@amiramw Could you finish the review? If it works then let's merge, code wise it looks good to me.

@amiramw
Copy link
Member

amiramw commented Jan 22, 2020

Tested successfully and code looks good to me.

@amiramw amiramw merged commit 9fb6351 into eclipse-theia:master Jan 22, 2020
@akosyakov
Copy link
Member

@amiramw @tomer-epstein please check the git history next time, there are 3 commits in this PR for one file change :( https://github.com/eclipse-theia/theia/blob/master/doc/pull-requests.md#checklist-commit-history

@tomer-epstein tomer-epstein deleted the vscode.openFolder branch January 23, 2020 06:40
@tomer-epstein
Copy link
Contributor Author

tomer-epstein commented Jan 23, 2020

@akosyakov can you pls update #4050
[x] vscode.openFolder - Open a folder or workspace in the current window or new window

@amiramw
Copy link
Member

amiramw commented Jan 23, 2020

@amiramw @tomer-epstein please check the git history next time, there are 3 commits in this PR for one file change :( https://github.com/eclipse-theia/theia/blob/master/doc/pull-requests.md#checklist-commit-history

Sorry. I missed that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
vscode issues related to VSCode compatibility
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants