Skip to content

Exclude composite literals from goconst instead of raising its threshold #124

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jugonzalez12 merged 1 commit into from
Sep 22, 2026
Merged

Exclude composite literals from goconst instead of raising its threshold #124

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions .golangci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,9 +40,8 @@ linters:
exhaustive:
default-signifies-exhaustive: true
goconst:
# goconst v1.9.0 reports literals inside composite literals; these hold the prior signal.
ignore-map-keys: true
min-occurrences: 6
# goconst v1.9.0 reports literals inside composite literals. Call is the upstream default; keep it.
exclude-types: [Call, CompositeLit]
gocritic:
enabled-checks:
- ruleguard
Expand Down