Support workspace settings

Adding hidesExplorerArrows and folders.associations has no affect if they’re added to workspace settings. No prompt is shown to restart and restarting does not apply the changes

When the same settings are added to user settings, a prompt is displayed to restart VS Code and are correctly displayed when VS Code is restarted.

Although it appears the user settings are remembered, as removing folders.associations keeps the set folder icons - so didn’t notice this didn’t work when I first moved the settings on device 1. Saving as an empty object first removes the associations on restart

Settings used

"material-icon-theme.hidesExplorerArrows": true,
"material-icon-theme.folders.associations": {
	"report": "docs",
    "implementation": "docs",
    "pyg": "temp",
    "bin": "config",
	"hibari": "components",
	"json_api": "components",
	"kitsu": "components"
}

[PKief]

Great news: the extension finally also supports workspace settings! 🎉

Tendentially, I would still recommend using the global user settings as often as possible if you want to customize something in the extension. If you jump into another VS Code window that contains different workspace settings, you will notice that it takes a moment for the icon extension to adapt to the new workspace. So if you want to adjust the extension on workspace level, I would recommend to do it only for the File or Folder associations, because it works fastest that way. Well, I’m already writing too much, just try it out 😉 I look forward to your feedback!

[PKief]

I recently tried to work on this feature. The conclusion from my side was that it’s still not really feasible, because all workspaces are using the same global icon configuration which is stored in the central extension folder. So it would be possible to load the workspace settings and to adjust the icons without reloading (for some settings). But if you’ve multiple workspaces opened at the same time, and open another workspace with different icon settings, it will change all icons of all opened workspaces, too. And this behavior is in my opinion not really nice and may look like a bug. It’s still not feasible to implement this feature the way I wish it would work.