-
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
plugins: add workbench.action.openSettings #7320
Conversation
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>
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.
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.
It supposed to accept some optional 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. |
@vince-fugnitto Could you have a look what |
It looks like it is used to add a Since we do not have such a concept at the moment, I assume it is fine to omit the |
Sounds good, please file a follow-up issue. |
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.
LGTM
|
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
Ext: Open Settings
master
)Review checklist
Reminder for reviewers
Signed-off-by: vince-fugnitto vincent.fugnitto@ericsson.com