Discontinue custom functionality support and get fully official

According to vscode #11751 next vscode release ❤️ will support icons here:

• open editors view
• tabs
• title in editor when tabs are disabled
• search results
• problems
• quick open / editor pickers

I’m thinking of removing all the custom functionality which now will only get reduced to:

• show/hide folders
• show/hide some specific icons
• show/hide tab icons
• show/hide open editors
• associate icons via regex

I’m fairly certain that VSCode team will implement at least these show/hide options in order to let the user choose where to show his/her icons.

For us it will allow us to get rid of all the admin rights madness and all these “hacky” implementations.

@bpasero, @aeschli are you planning to let the users enable / disable certain icon appearances?

I’m willing to leave the unofficial support as this is creating some issues to the VSCode team and it looks to me that this next release is the right time to do it. The main point of making this extension was bringing icons to VSCode and here they are. It’s just a matter of time for this functionality to evolve inside the VSCode project and hopefully they will provide some kind of user abilities in order to allow support for custom extensions (e.g. webpack.config.*.js)

It’s not a final decision but I somehow feel that this is the end of a cycle. Any thoughts?

[jens1o]

Please, please support “associate icons via regex”… I kinda like it, and some icons can’t be bound, because of these various file endings, for example Webconfig. (For example *.meta.tpl is json in my enviroment, but I still need the tpl Functions there)

These show/hide should be supported till Code supports it. I really like these options…

[bpasero]

@robertohuertasm I see, I leave it up to @aeschli to comment on such a support