missing config allow-leading-space for nolintlint

[vincentscdc]

Welcome

• Yes, I'm using a binary release within 2 latest major releases. Only such installations are supported.
• Yes, I've searched similar issues on GitHub and didn't find any.
• Yes, I've included all information below (version, config, etc).
• Yes, I've tried with the standalone linter if available. (https://golangci-lint.run/usage/linters/)

Description of the problem

the setting allow-leading-space for nolintlint is not part of the NoLintLint settings

Version of golangci-lint

$ golangci-lint --version
# 1.48.0

Configuration file

$ cat .golangci.yml

[linters-settings.nolintlint]
require-explanation = true
require-specific = true
allow-leading-space = true

Go environment

$ go version && go env
# go1.19

Verbose output of running

$ golangci-lint cache clean
$ golangci-lint run -v
# unneeded

Code example or link to a public repository

// add your code here

[boring-cyborg]

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

[nhatthm]

Same here.

I use this configuration

linters-settings:
  nolintlint:
    # Disable to ensure that nolint directives don't have a leading space.
    # Default: true
    allow-leading-space: false

however golangci-lint still reports issues with // nolint...

[ldez]

Hello,

Due to a change of go fmt inside go1.19.
We have to enforce the directive style.

So the option allow-leading-space has been dropped.

The syntax of directives is: [a-zA-Z]+:[a-zA-Z\-0-9]+.
The spaces around : and after the // must be removed.

If you do that your IDE (ex: goland) will format the directive as a directive and it will not add extra space.

Related to:
#3002
#1658 (comment)

[tstraley]

@ldez can you please update the documentation if this setting has been removed? https://golangci-lint.run/usage/linters/#nolintlint