A linter that suggests interface types. In other words, it warns about the usage of types that are more specific than necessary.
Patterns to include in execution and reports.
Note: Inspecode runs interfacer for each Go package and the input patterns are used for selecting Go packages containing input files. Therefore, the files excluded by the patterns are processed if they are contained in Go packages that also contain input files, and you may even see logs related to the excluded files in the job console. However, Inspecode eventually ignores any issues detected on the excluded files when generating job reports.
Patterns to exclude from execution and reports.
Note: Just like
input:. the ignore patterns may not applied completely when running interfacer.
Amount of CPU. The default machine has
0.75 CPU with
2880 MiB RAM.
No tool specific severity levels are available.
Note: The incremental analysis cannot be supported for interfacer. This is because interfacer requires a set of buildable files or packages to work and the results on unchanged files can be affected by changed files.
With default options:
inspecode: interfacer: default
With custom machine:
inspecode: interfacer: machine: cpu: 1.5 # 1.5 CPU, 5760 MiB RAM
interfacer requires all the dependencies to build, so Inspecode resolves the dependencies in the same manner as
go test. See the
go test page for the details.