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

FIX Issue 6955 - workbench.action.closeActiveEditor command #6978

Merged
merged 1 commit into from
Jan 29, 2020
Merged

FIX Issue 6955 - workbench.action.closeActiveEditor command #6978

merged 1 commit into from
Jan 29, 2020

Conversation

tomer-epstein
Copy link
Contributor

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

FIX Issue 6955 - workbench.action.closeActiveEditor command doesn't close a WebviewWidget

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

Issue: #6955

What it does

This change proposal adds a check whether a given widget is an editor in VS Code sense and can be closed.

How to test

  1. git clone https://github.com/tomer-epstein/vscode-close-editor.git
  2. cd vscode-close-editor && npm run compile && npm run package
  3. copy vscode-close-editor-0.0.1.vsix to plugins folder
  4. Click on a editor title (right) , choose 'VSCode Close Active Editor' / 'VSCode Close Other Editors' or 'VSCode Close All Editors'.

image

image

Review checklist

Reminder for reviewers

@amiramw
Copy link
Member

amiramw commented Jan 28, 2020

@tomer-epstein

  1. When i test without your fixes it seems that closeAllEditors, closeEditorsToTheRight, closeEditorsToTheLeft and closeOtherEditors work fine with webviews without your fix. Am I missing something?
  2. What is the expected behavior of closeEditorsInGroup and closeEditorsInOtherGroups?

@akosyakov akosyakov added the vscode issues related to VSCode compatibility label Jan 29, 2020
@akosyakov
Copy link
Member

@amiramw could you finish the review please? i will comment if see something

@tomer-epstein
Copy link
Contributor Author

tomer-epstein commented Jan 29, 2020

@tomer-epstein

  1. When i test without your fixes it seems that closeAllEditors, closeEditorsToTheRight, closeEditorsToTheLeft and closeOtherEditors work fine with webviews without your fix. Am I missing something?
  2. What is the expected behavior of closeEditorsInGroup and closeEditorsInOtherGroups?

@amiramw where did you test? on which env? did you test via vscode-close-editor vsix?

Copy link
Member

@amiramw amiramw left a comment

Choose a reason for hiding this comment

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

Code LGTM and tested successfully before and after the fix.

I did see a difference in close editors in group behavior. In vs code it closes all editors in group while here we close all editors except current one. @tomer-epstein please open a separate issue for that as I don't think it should block this PR.

@tomer-epstein
Copy link
Contributor Author

tomer-epstein commented Jan 29, 2020

issue has been opened : #6997

@amiramw
Copy link
Member

amiramw commented Jan 29, 2020

@tomer-epstein can you fix the cut off commit message?

@tomer-epstein tomer-epstein changed the title FIX Issue 6955 - workbench.action.closeActiveEditor command doesn't c… FIX Issue 6955 - workbench.action.closeActiveEditor command Jan 29, 2020
@amiramw amiramw merged commit e549212 into eclipse-theia:master Jan 29, 2020
@tomer-epstein tomer-epstein deleted the workbench.action.closeActiveEditor branch January 29, 2020 11:08
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