Add an extraThemes option to load more supported themes to allow user to switch when they want?

[JackTheMico]

So I have this need: sometimes I get bored with the current dracula theme, and I want to change it to catppuccin-mocha without rebuild nvf.
I take a look at the vim.theme code, I'm wondering if we can add an extraThemes option to load more themes chosed by users. In this way, users should be able to switch themes with colorscheme or Snacks.picker.colorschemes().
Fake code may look like:

{
  options.vim.theme = {
    enable = mkOption {
      type = bool;
      description = "Enable theming";
    };
    name = mkOption {
      type = enum (attrNames supportedThemes);
      description = ''
        Supported themes can be found in {file}`supportedThemes.nix`.
        Setting the theme to "base16" enables base16 theming and
        requires all of the colors in {option}`vim.theme.base16-colors` to be set.
      '';
    };
    extraThemes = mkOption {
      type = listOf (attrNames supportedThemes);
      description = ''
        Extra Themes to be loaded.
        Supported themes can be found in {file}`supportedThemes.nix`.
        Setting the theme to "base16" enables base16 theming and
        requires all of the colors in {option}`vim.theme.base16-colors` to be set.
      '';
    };
    base16-colors = base16Options;

    style = mkOption {
      type = enum supportedThemes.${cfg.name}.styles;
      description = "Specific style for theme if it supports it";
    };
    transparent = mkOption {
      type = bool;
      default = false;
      description = "Whether or not transparency should be enabled. Has no effect for themes that do not support transparency";
    };

    extraConfig = mkOption {
      type = lines;
      description = "Additional lua configuration to add before setup";
    };
  };

  config = mkIf cfg.enable {
    vim = {
      startPlugins = [cfg.name cfg.extraThemes];
      luaConfigRC.theme = entryBefore ["pluginConfigs" "lazyConfigs"] ''
        ${cfg.extraConfig}
        ${supportedThemes.${cfg.name}.setup {inherit (cfg) style transparent base16-colors;}}
      '';
      # TODO: setup all extraThemes with default settings.
    };
  };
}

Does this make sense? Or there's some better alternatives?

[NotAShelf]

This is an interesting idea, but could we not simply use the startPlugins inside the user configuration directly? Since there is no setup for extra themes, it ends up as an alias to `startPlugins. Feel free to correct me here, I would love to support more use cases but this strikes me as a case where we add an alias and nothing else. Unless there is something I am missing?

[JackTheMico]

You are right, there's no need to add a new alias since startPlugins works. Thank you for answering.