goconst: surface ExcludeTypes[CompositeLit] toggle in linter settings

[mikkeldamsgaard]

Welcome

• Yes, I've searched similar issues on GitHub and didn't find any.
• I agree to follow this project's Code of Conduct.

How did you install golangci-lint?

Official binary

Your feature request related to a problem? Please describe

goconst's Config.ExcludeTypes map can suppress findings by AST context (Assignment, Binary, Case, Return, Call, CompositeLit). golangci-lint only surfaces the Call entry, via ignore-calls.

There is no way to opt out of CompositeLit from config. Since v2.12 bundled goconst v1.9.0+, which added composite-literal element walking, every string used as a map key, struct field value, or slice element is now reported:

metav1.TypeMeta{APIVersion: "v1", Kind: "ConfigMap"}
map[string]any{"phase": "Pending", "message": "..."}

In a repo with Pulumi stacks and Kubernetes controllers, the v2.11 → v2.12 bump took us from ~5 to 383 findings, ~95% of them inside composite literals.

Describe the solution you'd like

Surface ExcludeTypes[CompositeLit] (and ideally the other Type values) in the goconst linter settings, the same way ExcludeTypes[Call] is surfaced today via ignore-calls.

Describe alternatives you've considered

• linters.exclusions.rules with path: — drops goconst wholesale on the affected directories.
• goconst.ignore-string-values listing every repeated Helm key / Kubernetes Kind / apiVersion — needs ~70 lines of yaml that grows with every new chart.
• source:-regex exclusion matching ^\s*"[^"]+":\s* — covers map-key lines but not struct-field-value lines.

All three are workarounds for a knob that already exists in the underlying linter.

Additional context

• goconst v1.10.0 Type enum: https://github.com/jgautheron/goconst/blob/v1.10.0/parser.go
• Bump that introduced the visitor change: PR build(deps): bump github.com/jgautheron/goconst from 1.8.2 to 1.9.0 #6421 (v1.8.2 → v1.9.0).
• Versions: golangci-lint v2.12.2, goconst v1.10.0.

Supporter

• I am a sponsor/backer of this project.

[boring-cyborg]

Hey, thank you for opening your first Issue ! 🙂 If you would like to contribute we have a guide for contributors.

[ldez]

This issue has not be created with the issue template, it just fake it.

So this is probably an AI generated issue.

[ldez]

I will update the issue template to kill immediately this kind of issue because GitHub doesn't want to allow disabling the usage of "blank issue".

[mikkeldamsgaard]

Not AI generated. I certainly used an agent to assist me in describing the issue, as it tends to include more context than i would. No offence ment here, just came across this while upgrading the linter on our project and thought it might have wider interest than us.