You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am building a super simple extension that associates a JSON Schema for my file package.manifest from SchemaStore.org and then with the languages contributionPoint are able to ensure that the json language is applied to it & thus the Schema is immediately available.
Continuing this I thought it would be neat to have a custom icon for my file, my initial thought is that I could extend an already icon theme that the user has set/defined in VSCode. So when contributing an Icon set from an extension my assumption if providing a very limited/tiny JSON of associations in my case just for the filenames package.manifest it would display & work against my chosen/active icon theme.
Otherwise I have a tedious task of duplicating or extending this JSON file with say the default VSCode Icon JSON file.
I am building a super simple extension that associates a JSON Schema for my file
package.manifest
from SchemaStore.org and then with thelanguages
contributionPoint are able to ensure that thejson
language is applied to it & thus the Schema is immediately available.Continuing this I thought it would be neat to have a custom icon for my file, my initial thought is that I could extend an already icon theme that the user has set/defined in VSCode. So when contributing an Icon set from an extension my assumption if providing a very limited/tiny JSON of associations in my case just for the filenames
package.manifest
it would display & work against my chosen/active icon theme.Otherwise I have a tedious task of duplicating or extending this JSON file with say the default VSCode Icon JSON file.
My limited icon JSON file
The text was updated successfully, but these errors were encountered: