Question 1

How to ignore string literals in logging calls with goconst?

Accepted Answer

Use the -ignore-calls flag with a comma-separated list of function names, e.g., goconst -ignore-calls slog.Info,fmt.Errorf ./, to exclude strings from those calls and reduce noise in logs.

Question 2

goconst vs golangci-lint for duplicate strings?

Accepted Answer

goconst offers specialized, configurable detection for exact literal duplication with flags like -min-length and -numbers, while golangci-lint is a broader linter that may include similar checks but with less fine-grained control. goconst is better for targeted refactoring tasks.

Question 3

Can goconst detect repeated numbers in Go code?

Accepted Answer

Yes, enable number detection with the -numbers flag. You can also set value ranges using -min and -max to focus on specific numeric literals, such as goconst -numbers -min 60 -max 512 .

Question 4

How to output goconst results in JSON format?

Accepted Answer

Run goconst with -output json, e.g., goconst -output json ./, to get structured data that can be parsed by other tools. This is useful for integrating into CI/CD pipelines or generating automated reports.

Question 5

What's the default minimum string length for goconst?

Accepted Answer

By default, goconst reports strings with a minimum length of 3 runes, but you can adjust this with the -min-length flag to ignore shorter literals, like common prefixes or abbreviations.

Question 6

Does goconst work with constant expressions?

Accepted Answer

Yes, with the -eval-const-expr flag enabled, goconst can evaluate constant expressions such as Prefix + 'suffix' to find duplication, which helps in codebases where constants are built from parts.

goconst

What is goconst?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions