Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

feature: selectively ignoring plugins #148

Open
1 task done
chrisgrieser opened this issue Mar 29, 2023 · 0 comments
Open
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
@aarondill
implement opts.library.blacklist (folke#148)
7bd2f2f 
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 aarondill mentioned this issue Sep 5, 2023
Open
aarondill added a commit to aarondill/neodev.nvim that referenced this issue Sep 5, 2023
@aarondill
feat: implement opts.library.blacklist (folke#148)
9c98ec9 
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@chrisgrieser