Can't make it work

[mgzenitech]

So I have this bit set for .env files linting using poe wrapper around dotenv-linter:

"any-lint.linters": [
    {
      "args": [
        "poe",
        "lint:dotenv",
        "-f",
        "${file}"
      ],
      "binPath": "poetry",
      "condition": "$.fileExtname.endsWith('.env')",
      "cwd": "${workspaceFolder}",
      "diagnostic": {
        "format": "${file}:${startLine} ${message}",
        "output": "stdout"
      },
      "name": "dotenv-linter",
      "on": [
        "change",
        "save"
      ]
    }
  ]

Output I get in any-lint:

/home/xxx/Documents/Projects/xxx/prototype-generic-vscode
poetry poe lint:dotenv -f /home/xxx/Documents/Projects/xxx/prototype-generic-vscode/.internal/.src/.env/.0.env
poetry poe lint:dotenv -f /home/xxx/Documents/Projects/xxx/prototype-generic-vscode/.internal/.src/.env/.0.env failed
.internal/.src/.env/.0.env:1 SpaceCharacter: The line has spaces around equal sign

Yet no problems are appearing in VSCode? What I'm doing wrong?

[Mart007King]

Try this:

• Ensure Extension is Installed and Enabled: Verify that the any-lint extension is installed and enabled in your VSCode setup.
• Restart VSCode: Sometimes, a simple restart can resolve issues related to configuration changes not being picked up.
• Check for Conflicts: Ensure no other linters or extensions are interfering with the output parsing.

[mgzenitech]

Try this:

* Ensure Extension is Installed and Enabled: Verify that the any-lint extension is installed and enabled in your VSCode setup.

* Restart VSCode: Sometimes, a simple restart can resolve issues related to configuration changes not being picked up.

* Check for Conflicts: Ensure no other linters or extensions are interfering with the output parsing.

Yeah, everything is enabled and installed properly as I can see the output of this extension:

Also tried reloading window multiple times.

Not sure how to debug this as there is no --debug switch or anything in extension settings

[tamayika]

Hi, thanks for the report. I've fixed the problem in 0.2.2. startColumn was a required placeholder in format but I changed it optional. If the problem still happens in the latest extension, please re-open this issue.