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
I'm not sure if this is a good idea or not, but we're currently finding that we're linting different parts of code to different standards. It would be nice to have lint-review test different parts of our code with different rulesets.
Currently we just ignore the warnings from lint-review, or just disable those tests across the entire repo.
You can ignore specific directories using the files.ignore config. Some linters support per directory config files for this purpose. Rubocop for example does this.
Why are different directories subject to different coding standards?
I'm not sure if this is a good idea or not, but we're currently finding that we're linting different parts of code to different standards. It would be nice to have lint-review test different parts of our code with different rulesets.
Currently we just ignore the warnings from lint-review, or just disable those tests across the entire repo.
For example we're not as strict on docstrings in our tests because unittest sometimes uses the docstring as the test description (https://docs.python.org/2/library/unittest.html#unittest.TestCase.shortDescription).
The text was updated successfully, but these errors were encountered: