Run custom linter without changing the source code of golangci-lint

[HaraldNordgren]

For our project, we are using gometalinter with a config to allow running our own linter called "go-corp-linter" like this:

.gometalinter.json:

{
  "Deadline": "2m",
  "Vendor": true,
  "Test": true,

  "Enable": [
    "deadcode",
    "errcheck",
    "goconst",
    "golint",
    "gotype",
    "gotypex",
    "ineffassign",
    "interfacer",
    "nakedret",
    "staticcheck",
    "structcheck",
    "unconvert",

    "go-corp-linter"
  ],

  "linters": {
    "go-corp-linter": "go-corp-linter:PATH:LINE:COL:MESSAGE"
  },

  "exclude": [
    ".+_mock(_test)?\\.go:"
  ]
}

We run the linter through gometalinter --config=scripts/.gometalinter.json ./...

I would like the same option with golangci-lint without having to clone the repo and change the source code.

[jirfag]

Hi!
The idea to run any linter contradicts golangci-lint's architecture: we reuse parsed/analyzed code. We don't analyze code repeatedly as gometalinter does.

But I'm planning to add support for any go/analysis` based linter without changing source code

[benjaminjkraft]

But I'm planning to add support for any go/analysis` based linter without changing source code

@jirfag Do you have any guess at a timeframe for this? Is it something where you'd welcome a PR? We're keen to start writing our own go/analysis-based linters specific to our codebase.

[jirfag]

No timeframe, pull requests are welcome

[dbraley]

#841

[jirfag]

thank you,
now you can use plugins for that, see docs.