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

Allow setting custom labels for settings in the UI #83663

Closed
DanTup opened this issue Oct 30, 2019 · 3 comments
Closed

Allow setting custom labels for settings in the UI #83663

DanTup opened this issue Oct 30, 2019 · 3 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@DanTup
Copy link
Contributor

DanTup commented Oct 30, 2019

This was discussed a little in #50249, but as far as I can tell not addressed - nor can I find an open issue for it.

The labels shown in the settings editor are auto-generated from the settings keys (even though the code-completion in package.json suggests there is a title field):

Screenshot 2019-10-30 at 2 13 59 pm

Screenshot 2019-10-30 at 2 14 17 pm

Strangely, the build-in extensions seem to be able to handle this (for example there are lots with HTML in them), but I can't find how this is achieved (possibly they have special localisation lookups we don't?).

@roblourens
Copy link
Member

This is covered by #70589 and #51778.

There are a set of whitelisted terms like HTML and JavaScript that should be formatted correctly. Not a great solution, I think we need something better like what you suggest.

@roblourens roblourens added the *duplicate Issue identified as a duplicate of another issue(s) label Oct 30, 2019
@vscodebot
Copy link

vscodebot bot commented Oct 30, 2019

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.

Happy Coding!

@DanTup
Copy link
Contributor Author

DanTup commented Oct 30, 2019

Thanks - I somehow failed to find those ones! :-)

@vscodebot vscodebot bot locked and limited conversation to collaborators Dec 16, 2019
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)
Projects
None yet
Development

No branches or pull requests

2 participants