feat: ✨ loose icons

[lucas-labs]

allow icons that are not associated to any folder/file but that can be configured later by the user manually.

export type LucodearFileIcon = RequireAtLeastOne<
  BasicFileIcon & {
    looseFileIcon?: true;
    theme?: string;
  },
  'fileExtensions' | 'fileNames' | 'looseFileIcon'
>;

export type LucodearFolderIcon = RequireAtLeastOne<
  Omit<FolderIcon, 'folderNames'> & {
    theme?: string;
    looseFolderIcon?: true;
    folderNames?: string[];
  },
  'looseFolderIcon' | 'folderNames'
>;

Adds looseFileIcon and looseFolderIcon to the LucodearFileIcon and LucodearFolderIcons types, respectively.

Setting this fields to true allows defining an icon that is not "tied" to any file extension, name, folder name, etc, but they will be still present in the final extension definition json, so that the user can use them via configuration setting.

[github-actions]

Preview

Thank you for creating a pull request. This preview shows you how your changes will look on the different themes:

You can find more information how to contribute in the contribution guidelines.

[github-actions]

Preview

Thank you for creating a pull request. This preview shows you how your changes will look on the different themes:

You can find more information how to contribute in the contribution guidelines.

[github-actions]

Merge Successful

Thanks for your contribution! 🎉

The changes will be part of the upcoming update on the marketplace.