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

Settings key representation in visual settings editor #85421

Closed
go2sh opened this issue Nov 22, 2019 · 3 comments
Closed

Settings key representation in visual settings editor #85421

go2sh opened this issue Nov 22, 2019 · 3 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) info-needed Issue requires more information from poster

Comments

@go2sh
Copy link
Contributor

go2sh commented Nov 22, 2019

  • VSCode Version: 1.40.1
  • OS Version: Linux x64

Steps to Reproduce:

  1. Have an extension, where the name of the extension and the first part of settings keys differ.
  2. Open the visual settings editor
  3. Goto the extension settings

The first part of the key will be shown in the Title: e.g "C/C++ > ..." for the C/C++ Extension. I realized to late as there is no documentation about that, that the name of my extension and the first key element must match to get rid of it. It would be nice to have a way around that, like drop the first element from the view, if it is not the only element.

There are quite some extension out there, where the condition is met.

@roblourens
Copy link
Member

Can you give a specific example of what the problem is and what you suggest? I don't quite understand.

@roblourens roblourens added the info-needed Issue requires more information from poster label Nov 24, 2019
@go2sh
Copy link
Contributor Author

go2sh commented Nov 25, 2019

grafik
In the Snapshot you see the key "azure.cloud" with the Prefix "Azure: ", the name of the extension is "azure-account". So the first part of the key gets rendered as part of the title.
grafik
Compare it to the key "git.allowForcePush", the first part of the key didn't get rendered, as the settings key and the extension name match.

The first behavior happens alot as this is not part of the documentation, it would be nice to have a way to get the second behavior without matching extension name and setting key. It would make the settings easier to read.

@roblourens
Copy link
Member

Ok I see. There is an issue to give extensions more ability to customize their settings UI: #70589

@roblourens roblourens added the *duplicate Issue identified as a duplicate of another issue(s) label Nov 25, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

2 participants