You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Agreed on your findings, @uwehdaub.
Looks like it's better to always spawn the linter process from the current's file directory. Otherwise it breaks the ability of searching linters' config files if parent directories (yamllint in particular).
I've created some ignore rule in
.yamllint.yaml
like the followingWhen I run
yamllint
from the command line all works fine.But in VS-Code I still get a line to long error.
After some experimentation I stumbled about this in
.settings
which means,
yamllint
reads the file fromstdin
and obvious has no filename.I can get around this problem by calling
yamllint
with the filenamebut I have to re-write the ignore rules to
because it seems, that
yamllint
is not executed from the root of the workspace.After these changes my yaml files are linted as they were linted from the command line.
Is there anything that I miss, or is there a better way to tackle this problem?
The text was updated successfully, but these errors were encountered: