Replies: 5 comments 3 replies
-
|
Neat idea, it also can be integrated with But first of all, I think this will require support for a machine-readable output format. To make integrations possible |
Beta Was this translation helpful? Give feedback.
-
|
There is a way sorta to do it through any-lint. I haven't managed to completely make it work but my progress can be found here if anyone's interested: |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for sharing, I will try using it with ls-lint. https://ls-lint.org for reference |
Beta Was this translation helpful? Give feedback.
-
|
that's it working with any-lint already :) plugin author fixed the issue. |
Beta Was this translation helpful? Give feedback.
-
|
The only issue here is that More info @ tamayika/vscode-any-lint#1 So if any devs of this linter will add these (or similar) switches to cli: then any-lint will also be able to provide onType event info |
Beta Was this translation helpful? Give feedback.
-
|
For documentation purposes will leave also config here to run dotenv-linter through any-lint: "any-lint.linters": [
{
"args": [
"-q",
"${file}"
],
"binPath": "dotenv-linter",
"condition": "$.fileExtname.endsWith('.env')",
"cwd": "${workspaceFolder}",
"diagnostic": {
"format": "${file}:${startLine} ${message}",
"output": "stdout"
},
"name": "dotenv-linter",
"on": [
"change",
"save"
]
}
] |
Beta Was this translation helpful? Give feedback.
-
|
Here you go guys, I've made example config that adds full support for dotenv-linter via any-linter: For now only onsave event works as dotenv-linter has to add support for --stdin |
Beta Was this translation helpful? Give feedback.
-
I know almost zero about vscode plugins but a .env plugin using the validator would be cool.
At least a plugin that runs checks on save
Beta Was this translation helpful? Give feedback.
All reactions