Configuration per files

[azu]

Summary

Some use case multiple configuration in a project.

• lint manifest/*.yml with manifest rules
• lint "**/*" with recommended rules

It will gain performance, because reduce manifest rules works.

Currenlty, we can do this will by two steps:

1. secretlint --secretlintrc .secretlintrc.manifest.json "manifest/*.yml"
2. secretlint --secretlintrc .secretlintrc.json "**/*"

We need to optimize this pattern.

Basic example

ESlint resolve this issue by overrides config.

{
  "rules": {
    "quotes": ["error", "double"]
  },

  "overrides": [
    {
      "files": ["bin/*.js", "lib/*.js"],
      "excludedFiles": "*.test.js",
      "rules": {
        "quotes": ["error", "single"]
      }
    }
  ]
}

• https://eslint.org/docs/user-guide/configuring#example-configuration

Maybe, It is complex.

We need to think more reasonable solutions.

[azu]

I have a idea: add includes and excludes for each rule.
Secretlint use minimatch and target file before linting.

{
  "rules": [{
     "id": "example",
     "includes": ["**/*"],
     "excludes": ["ignored_dir/**"]
  }]
}

When run secretlint with above config

secretlint "**/*"

• target/test.txt: it is linted
• ignored_dir/text.txt: it is ignored

[azu]

#105 (comment)
This concept is that secretlintignore for a rule.
I think that this configuration is useful. It will improve performance and improve flexibility.
As Cons, It make a bit complexibility to codebase?

[moltar]

I think includes and excludes are necessary, and can unlock a lot of useful functionality, especially for monorepos, where rules might be per-package.