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

Support for Custom CompletionItemKind Icons #4201

Closed
rionmonster opened this issue Mar 14, 2016 · 5 comments
Closed

Support for Custom CompletionItemKind Icons #4201

rionmonster opened this issue Mar 14, 2016 · 5 comments
Assignees
Labels
api *as-designed Described behavior is as designed

Comments

@rionmonster
Copy link

I'm currently working on an extension for VS Code to add the functionality of another extension of mine that was created for Visual Studio: Glyphfriend. When I began working on this, I noticed that the CompletionItemKinds enum only seems to support a predefined set of values (e.g. Value,Text,File, etc.).

Is there any way to currently set this glyph to a specific file? Or is there another preferred way that I should look at implementing this type of behavior (either via a different type of provider or through somehow extending the existing CompletionItemKind class)?

Any feedback or recommendations would be appreciated.

@rionmonster rionmonster changed the title Support for Custom CompletionItemKind Glyphs Support for Custom CompletionItemKind Icons Mar 14, 2016
@egamma egamma added feature-request Request for new features or functionality api labels Mar 15, 2016
@sandyarmstrong
Copy link
Member

@jrieken
Copy link
Member

jrieken commented Aug 4, 2016

@sandyarmstrong which is very bad suggestion since there is no guarantee from our side (1) if that file will always exist at the location, (2) what class names etc we are going to use, (3) how our build pipeline inlines, rewrites icons, and (4) that the app signing will eventually think about that.

Everyone is always invited to help out (hello PRs) and it will be a lot more rewarding than a hack like that.

@sandyarmstrong
Copy link
Member

@jrieken in retrospect, I was thinking from the context of a consumer of monaco-editor, not a VS Code extension author. You're absolutely right.

@jrieken
Copy link
Member

jrieken commented Aug 4, 2016

Agreed - for the editor it's a slightly different game.

@jrieken jrieken added *as-designed Described behavior is as designed and removed feature-request Request for new features or functionality labels Apr 11, 2017
@jrieken
Copy link
Member

jrieken commented Apr 11, 2017

For the sake of making it easier to write and share language servers, esp wrt the language service protocol we will stick to a pre-defined set of icons and kinds.

@jrieken jrieken closed this as completed Apr 11, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
api *as-designed Described behavior is as designed
Projects
None yet
Development

No branches or pull requests

4 participants