tsOfficial setting is ignored

• I’m sure this issue is not a duplicate
• I want to create an icon request(if not, remove these lines below)

No matter if I set "vsicons.presets.tsOfficial": false to true or false, or even remove it entirely, I always see the official TS icon displayed in my files list:

[lumaxis]

@robertohuertasm None taken and absolutely fair point!

My biggest issue with this is discoverability and the way this differs from my (and I’m naively presuming other users’) expectation of how settings in VS Code work. I have not ever seen another built-in VS Code setting or extension setting that required me to execute a manual task without me explicitly prompting about it. And I really customize a lot of things 🙂

The only things that I have experienced so far are were extensions that either required me to reload/restart or click a button in the toast that showed after I changed a setting. The way vscode-icons handles this right now is in my opinion not optimally designed as it goes against everything I’m used to since the time I started using VS Code. I strongly disagree with you on this:

The idea of leaving this process completely unobstrusive was to not annoy the user with every time she changes the configuration.

While I agree that it’s a good goal to be unobtrusive, I don’t think it’s unreasonable to show a toast when a user manually changes a setting. Realistically, how often does a user change a preset? And when they do, are there many cases where they would not want to apply them?

My point boils down to this: It’s all good that this is documented and the documentation well written and clear but in my view, a well-designed system should be usable without having to read the documentation.

But then again, maybe this isn’t a problem for other users at all? The lack of other Issues about the same problem surprised me, so maybe I’m totally wrong here 🙂

[JimiC]

The think is that vscode itself uses the detection technic, upon saving the settings file, to enable/disable its features and settings. And this is what the user expects as a UX from the extensions as well. So @lumaxis has a strong point. On the other hand, we had our shares of complaints about being intrusive and we are now very cautious with it. There is also an issue on vscode about extensions messages being too annoying.

1. React only to changes affecting vscode-icons settings

I’m confident that this is achievable.

1. Allow the user to turn on/off this behavior.

This is the tricky part.