You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
If I want to specify extra args for linters, there's no provision for doing that. For conform.nvim, we have prepend_args and LazyVim merges the passed opts with the defaults.
Describe the solution you'd like
As it is with formatters, support for this would be great. For example, since nvim-lint does not have a prepend_args key, we could reserve this key just for LazyVim where the config() function extends the default linter with the passed args.
This would result in a clean config on the user side like this:
mfussenegger/nvim-lint#397 discusses this, but when I assigned a function for shellcheck doing the same list extension, it did not work as the function overrides the default linter table.
Additional context
For now, in my config I have the following if condition to implement this feature.
Did you check the docs?
Is your feature request related to a problem? Please describe.
If I want to specify extra args for linters, there's no provision for doing that. For
conform.nvim
, we haveprepend_args
and LazyVim merges the passed opts with the defaults.Describe the solution you'd like
As it is with formatters, support for this would be great. For example, since
nvim-lint
does not have aprepend_args
key, we could reserve this key just for LazyVim where theconfig()
function extends the default linter with the passed args.This would result in a clean config on the user side like this:
Describe alternatives you've considered
mfussenegger/nvim-lint#397 discusses this, but when I assigned a function for shellcheck doing the same list extension, it did not work as the function overrides the default linter table.
Additional context
For now, in my config I have the following if condition to implement this feature.
The text was updated successfully, but these errors were encountered: