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
When using the --exclude command line flag, Squawk ignores excludes that were loaded from the config file.
To me this is unexpected (other linters that I've used combine those), and makes the config file less useful (to me).
Is there a use case for ignoring the excludes from the config file, or can we just combine the excludes?
One case that I have not covered here is if the user wants to use both the CLI flags and the config file, one solution for this case would be to use the -c/--config flag together with the --exclude flag to signal the program that the user wants to merge those two together, but it's not a change that I want to do in this PR and it would be beneficial to reach an agreement with the contributors/community before deciding on a way to handle this case.
The text was updated successfully, but these errors were encountered:
When using the
--exclude
command line flag, Squawk ignores excludes that were loaded from the config file.To me this is unexpected (other linters that I've used combine those), and makes the config file less useful (to me).
Is there a use case for ignoring the excludes from the config file, or can we just combine the excludes?
This issue has been mentioned before in #213:
The text was updated successfully, but these errors were encountered: