Repository navigation
Linter: Make it possible to configure linter rules in the config file on per folder basis #354
Description
Our project has a unit testing directory, where tests are calling private functions (they start with _). For tests code the linter reports errors, that the private functions are called, but for our project we want to ignore them.
There only way to configure the linter I found from the docs is with comments and cli args, which is not scalable for the team or the whole bunch of unit tests files with hundreds of calls.
Activity
[-]Make it possible to configure linter rules in the config file on per folder basis[/-][+]Linter: Make it possible to configure linter rules in the config file on per folder basis[/+]NathanLovato commentedon Sep 14, 2026
Would editor config support, similar to how the formatter itself is configured, be a good solution for your team? There's a stub for configuring the linter from editorconfig files, although it's minimal: it's limited to the max line length at the moment. It can be extended to add custom fields for toggling rules.
gikari commentedon Sep 14, 2026
Yes, this is acceptable 👍