feature: Prevent cleaning dependencies of a plugin marked as conditional

[abeldekat]

Did you check the docs?

• I have read all the lazy.nvim docs

Is your feature request related to a problem? Please describe.

Example:

  {
    "gbprod/substitute.nvim",
    cond = false,
    event = "VeryLazy",
    dependencies = "tpope/vim-abolish"
  }

In lazy's UI, substitute.nvim is shown in the disabled section, using a different color.
Plugin vim-abolish is only used inside the spec of substitute.nvim.
However, vim-abolish is "just" disabled, and is shown in the clean section of the UI.

Describe the solution you'd like

When plugin A is marked as conditional, and plugin B is only used inside the dependencies of plugin A, plugin B should also be marked as conditional. This prevents plugin B from being cleaned.

Related: bug: plugins not loaded due to cond are not contained in the lazy-lock.json file
Perhaps it would make sense to not remove conditional plugins from lazy-lock.json.

Describe alternatives you've considered

...

Additional context

Folke, if you are interested in this proposal, I could write a PR or extend feat(core): If a plugin is not enabled, ignore all specs in its dependencies

[miki725]

is there anything you need to do not to clean disabled plugins from lock file? when I do :Lazy restore it removes all disabled plugins from the lock file. By disabled I mean things like:

{
  "plugin",
  cond = function()
     return false
  end
}