mirror of
https://github.com/jesseduffield/lazygit.git
synced 2024-12-08 10:56:22 +02:00
3e2ef84d56
This is pretty funny: the staticcheck linter gets mad if we use a field which is marked in a comment as being deprecated. But it tripped on my own comment saying that a field is deprecated in terms of the user config! Obviously we have to make use of this field, otherwise we would just remove it entirely rather than mark it as deprecated, so I'm silencing this lint. I doubt this lint would actually come in handy in other cases (like when using a third party package) and worst case scenario we just end up fixing the problem when we try to upgrade the package and the deprecated field is now gone).
35 lines
784 B
YAML
35 lines
784 B
YAML
linters:
|
|
disable:
|
|
- structcheck # gives false positives
|
|
enable:
|
|
- gofumpt
|
|
- thelper
|
|
- goimports
|
|
- tparallel
|
|
- wastedassign
|
|
- exportloopref
|
|
- unparam
|
|
- prealloc
|
|
- unconvert
|
|
- exhaustive
|
|
- makezero
|
|
- nakedret
|
|
# - goconst # TODO: enable and fix issues
|
|
fast: false
|
|
|
|
linters-settings:
|
|
exhaustive:
|
|
default-signifies-exhaustive: true
|
|
staticcheck:
|
|
# SA1019 is for checking that we're not using fields marked as deprecated
|
|
# in a comment. It decides this in a loose way so I'm silencing it. Also because
|
|
# it's tripping on our own structs.
|
|
checks: ["all", "-SA1019"]
|
|
nakedret:
|
|
# the gods will judge me but I just don't like naked returns at all
|
|
max-func-lines: 0
|
|
|
|
run:
|
|
go: '1.20'
|
|
timeout: 10m
|