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

plugins: add workbench.action.openSettings #7320

Merged
merged 1 commit into from
Mar 12, 2020
Merged

Conversation

vince-fugnitto
Copy link
Member

What it does

Fixes #7317

The following commit adds the workbench.action.openSettings command so that it can be executed successfully by VS Code extensions.

How to test

  1. include the following test vscode extension
  2. execute the command Ext: Open Settings
  3. the preferences widget should be correctly opened (this was not the case on master)

Review checklist

Reminder for reviewers

Signed-off-by: vince-fugnitto vincent.fugnitto@ericsson.com

Fixes #7317

The following commit adds the `workbench.action.openSettings` command
so that it can be executed successfully by VS Code extensions.

Signed-off-by: vince-fugnitto <vincent.fugnitto@ericsson.com>
@vince-fugnitto vince-fugnitto added the vscode issues related to VSCode compatibility label Mar 11, 2020
@vince-fugnitto vince-fugnitto self-assigned this Mar 11, 2020
Copy link
Contributor

@Anasshahidd21 Anasshahidd21 left a comment

Choose a reason for hiding this comment

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

LGTM, I tried testing it on master, it didn't open the preferences and just fallback to the current editor.
With the PR, it successfully opens the preferences.

@akosyakov
Copy link
Member

@ishche
Copy link
Contributor

ishche commented Mar 12, 2020

Not sure how it is important right now, cc @ishche ?

For us, it's nice to have. But we can do a workaround for that.

@akosyakov
Copy link
Member

@vince-fugnitto Could you have a look what query supposed to do and whether we can do it. I assume it is something like to select a tree node with our tree APIs it should not be hard.

@vince-fugnitto
Copy link
Member Author

@vince-fugnitto Could you have a look what query supposed to do and whether we can do it. I assume it is something like to select a tree node with our tree APIs it should not be hard.

It looks like it is used to add a query search term to the widget (ex: passing 'vince'):

image

Since we do not have such a concept at the moment, I assume it is fine to omit the query for the moment?

@akosyakov
Copy link
Member

Since we do not have such a concept at the moment, I assume it is fine to omit the query for the moment?

Sounds good, please file a follow-up issue.

Copy link
Member

@akosyakov akosyakov left a comment

Choose a reason for hiding this comment

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

LGTM

@vince-fugnitto
Copy link
Member Author

Since we do not have such a concept at the moment, I assume it is fine to omit the query for the moment?

Sounds good, please file a follow-up issue.

#7328

@vince-fugnitto vince-fugnitto merged commit a546178 into master Mar 12, 2020
@vince-fugnitto vince-fugnitto deleted the vf/GH-7317 branch March 12, 2020 13:19
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.

workbench.action.openSettings is missing
4 participants