[product icon themes] No fallback for using icon contribution point
See original GitHub issueTesting #117263
While it’s been nice to leverage custom icons from another extension:
There doesn’t seem to be a way to set a fallback in case a user does not have the custom icon extension installed:
I guess you could mark that other extension as a dependency, but that would make it harder to use and would love for an easier way. We should allow for a fallback icon that uses a codicon
icon.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Product Icon Theme | Visual Studio Code Extension API
To define your own product icon theme, start by creating a VS Code extension and add the productIconThemes contribution point to the extension's...
Read more >116695 – Default icon theme for Gnome based desktop ...
Currently, the default icon theme takes the fallback if the desktop environment is not KDE or Unity. Better we change this to Gnome...
Read more >How do I write a VSCode extension to set a file icon for ...
You can follow issue 14662. VScode 1.64 (Jan. 2022) should include issue 140047: "finalize icon property of the language contribution point" ...
Read more >Icon Theme Specification
It is recommended that the icons installed in the hicolor theme look neutral, since it is a fallback theme that will be used...
Read more >Add a web app manifest
To use SVG icons safely, you should always specify a rasterized icon as a fallback for browsers that do not support SVG icons....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks, fixed the missing warning and validation of required properties,
Hi @aeschli ,
That’s great! It indeed does work, BUT with a few changes/limitations:
id
cannot have.
(dots)description
If I use
project-manager.favorites.codespaces
as icon’s id, it will fail. It will display theerror
codicon instead. I tried a few scenarios and discovered that the.
(dot character) was the reason. Yes, there is a regex to validate the icon’s id, but it does not warn about the dot character not being supported (if this is intentional).Doing these changes, I could see it working perfectly:
Thank you