Looking to leverage both no-unaliased and no-extra-aliasedflags in golangci-lint, and end up getting results where un-aliased imports start giving problematic results. Ideally we'd have the restrictions provided by both the flags (consistent, always-defined aliases; rejecting any new aliases that aren't described)
Looking to leverage both
no-unaliased
andno-extra-aliased
flags in golangci-lint, and end up getting results where un-aliased imports start giving problematic results. Ideally we'd have the restrictions provided by both the flags (consistent, always-defined aliases; rejecting any new aliases that aren't described)Which results in a number of issues, where even standard libraries act as if they have an alias but not in the config: