plugins: migrate defaultPackage -> package

Migrate all users of `mkVimPlugin` and `mkNeovimPlugin` to use the new
`package` argument instead of the old `defaultPackage` argument.
This commit is contained in:
Matt Sturgeon 2024-09-02 14:05:11 +01:00
parent 285f6cbd7b
commit 1fd4b6c739
No known key found for this signature in database
GPG key ID: 4F91844CED1A8299
148 changed files with 126 additions and 277 deletions

View file

@ -16,13 +16,12 @@ with lib;
colorscheme ? name,
# options
originalName ? name,
# WARNING: `defaultPackage` is deprecated by `package`,
defaultPackage ? throw "mkVimPlugin called without either `package` or `defaultPackage`.",
# Can be a string, a list of strings, or a module option:
# - A string will be intrpreted as `pkgs.vimPlugins.${package}`
# - A list will be interpreted as a "pkgs path", e.g. `pkgs.${elem1}.${elem2}.${etc...}`
# - An option will be used as-is, but should be built using `lib.mkPackageOption`
package ? helpers.mkPluginPackageOption originalName defaultPackage,
# Defaults to `name`, i.e. `pkgs.vimPlugins.${name}`
package ? name,
settingsOptions ? { },
settingsExample ? null,
globalPrefix ? "",