cosmos-sdk/tools/gometalinter.json

{
    "Linters": {
        "vet": "go tool vet -composites=false :PATH:LINE:MESSAGE"
   },
    "Enable": ["golint", "vet", "ineffassign", "unparam", "unconvert", "misspell"],
    "Deadline": "500s",
    "Vendor": true,
    "Cyclo": 11,
    "Exclude": ["/usr/lib/go/src/"]
}
tools: Switch gometalinter to use a config file 2018-07-07 12:00:06 -07:00			`{`
			`"Linters": {`
			`"vet": "go tool vet -composites=false :PATH:LINE:MESSAGE"`
			`},`
tools: Remove gocyclo We can investigate re-introducing our own fork #postlaunch. Closes #2211 2018-09-03 21:29:59 -07:00			`"Enable": ["golint", "vet", "ineffassign", "unparam", "unconvert", "misspell"],`
tools: Switch gometalinter to use a config file 2018-07-07 12:00:06 -07:00			`"Deadline": "500s",`
tools: Add code complexity linter, gocyclo Gocyclo is a code complexity linter. It uses cyclomatic complexity. Cyclomatic complexity essentially measures the number of different paths code could go through. (The conditional in a for loop counts as adding one path) It looks at this on a per-function level. The idea that this would be enforcing is that if there are too many different paths code can go through in a function, it needs to be better split up. (A function with too many code paths is hard to reason about) The complexity which we want the linter to start failing on is configurable. The default is 10. Change the "Cyclo" parameter in `tools/gometalinter.json` to try other values. 2018-07-07 18:59:06 -07:00			`"Vendor": true,`
Merge PR #2219: Update to Tendermint 0.24 (except NextValSet offsets) 2018-10-03 08:48:23 -07:00			`"Cyclo": 11,`
			`"Exclude": ["/usr/lib/go/src/"]`
			`}`