Skip to content
This repository has been archived by the owner on Jul 6, 2024. It is now read-only.

feature: selectively ignoring plugins #148

Closed
1 task done
chrisgrieser opened this issue Mar 29, 2023 · 0 comments
Closed
1 task done

feature: selectively ignoring plugins #148

chrisgrieser opened this issue Mar 29, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@chrisgrieser
Copy link

Did you check the docs?

  • I have read all the neodev.nvim docs

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

Some plugins have bad annotations, e.g. parameters not being marked as optional. When setting plugins = true, this results in superfluous warnings.

Describe the solution you'd like

Right now, the plugins setting only allows to either enable/disable all plugins, or to enable individual plugins (whitelisting).

I would propose to selectively ignore plugins (blacklisting), since it is a few, but not the majority of plugins with such bad annotations.

Describe alternatives you've considered

  • enable all plugins, and use @diagnostic disable a lot. Works, but very cumbersome if you have many plugins with bad annotations
  • enable only plugins with proper annotations. Works, but you you have to manually add dozens of plugins, which is even more cumbersome

Additional context

No response

@chrisgrieser chrisgrieser added the enhancement New feature or request label Mar 29, 2023
aarondill added a commit to aarondill/neodev.nvim that referenced this issue Sep 5, 2023
This PR implements folke#148 by adding a new option (`opts.library.blacklist`) which is a string[] that consists
of plugin names (just as `opts.library.plugins`) which will not be included in the final path.

Note: This overrides `opts.library.plugins` in that, if a plugin is included in the blacklist, it *will not*
be included, even if included in the `plugins` list.
aarondill added a commit to aarondill/neodev.nvim that referenced this issue Sep 5, 2023
This PR implements folke#148 by adding a new option (`opts.library.blacklist`) which is a string[] that consists
of plugin names (just as `opts.library.plugins`) which will not be included in the final path.

Note: This overrides `opts.library.plugins` in that, if a plugin is included in the blacklist, it *will not*
be included, even if included in the `plugins` list.
@folke folke closed this as completed Jul 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants