woodpecker/vendor/github.com/OpenPeeDeeP/depguard

Depguard

Go linter that checks package imports are in a list of acceptable packages. It can also deny a list of packages and can do prefix or glob matching. This allows you to allow imports from a whole organization or only allow specific packages within a repository. It is recommended to use prefix matching as it is faster than glob matching. The fewer glob matches the better.

If a pattern is matched by prefix it does not try to match via glob.

Install

go get -u github.com/OpenPeeDeeP/depguard

Config

By default, Depguard looks for a file named .depguard.json in the current current working directory. If it is somewhere else, pass in the -c flag with the location of your configuration file.

The following is an example configuration file.

{
  "type": "allowlist",
  "packages": ["github.com/OpenPeeDeeP/depguard"],
  "packageErrorMessages": {
    "github.com/OpenPeeDeeP/depguards": "Please use \"github.com/OpenPeeDeeP/depguard\","
  },
  "inTests": ["github.com/stretchr/testify"],
  "includeGoStdLib": true
}

• type can be either allowlist or denylist. This check is case insensitive. If not specified the default is denylist. The values whitelist and blacklist are also accepted for backwards compatibility.
• packages is a list of packages for the list type specified.
• packageErrorMessages is a mapping from packages to the error message to display
• inTests is a list of packages allowed/disallowed only in test files.
• Set includeGoStdLib (includeGoRoot for backwards compatibility) to true if you want to check the list against standard lib. If not specified the default is false.

Ignore File Rules

The configuration also allows us to specify rules to ignore certain files considered by the linter. This means that we need not apply package import checks across our entire code base.

For example, consider the following configuration to block a test package:

{
  "type": "denylist",
  "packages": ["github.com/stretchr/testify"],
  "inTests": ["github.com/stretchr/testify"]
}

We can use a ignoreFileRules field to write a configuration that only considers test files:

{
  "type": "denylist",
  "packages": ["github.com/stretchr/testify"],
  "ignoreFileRules": ["!**/*_test.go"]
}

Or if we wanted to consider only non-test files:

{
  "type": "denylist",
  "packages": ["github.com/stretchr/testify"],
  "ignoreFileRules": ["**/*_test.go"]
}

Like the packages field, the ignoreFileRules field can accept both string prefixes and string glob patterns. Note in the first example above, the use of the ! character in front of the rule. This is a special character which signals that the linter should negate the rule. This allows for more precise control, but it is only available for glob patterns.

Gometalinter

The binary installation of this linter can be used with Gometalinter.

If you use a configuration file for Gometalinter then the following will need to be added to your configuration file.

{
  "linters": {
    "depguard": {
      "command": "depguard -c path/to/config.json",
      "pattern": "PATH:LINE:COL:MESSAGE",
      "installFrom": "github.com/OpenPeeDeeP/depguard",
      "isFast": true,
      "partitionStrategy": "packages"
    }
  }
}

If you prefer the command line way the following will work for you as well.

gometalinter --linter='depguard:depguard -c path/to/config.json:PATH:LINE:COL:MESSAGE'

Golangci-lint

This linter was built with Golangci-lint in mind. It is compatible and read their docs to see how to implement all their linters, including this one.