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
Create a dangling symlink ln -s not-found.py symlink.py
Run vale vale . --output=JSON
Expected behaviour
The command is unaffected by the dangling symlink.
Actual behaviour
The command fails with
{
"Code": "E100",
"Text": "stat symlink.py: no such file or directory"
}
Notes
vale sync is not affected
I'm not sure whether this behaviour is completely incorrect, or if it makes sense for files that are actually being checked by vale — probably if I had a broken symlink to a Markdown file in my project, it would be okay if the command faild, but maybe the error message could be improved.
The text was updated successfully, but these errors were encountered:
Check for existing issues
Environment
Tested on:
Describe the bug / provide steps to reproduce it
vale.ini:
ln -s not-found.py symlink.py
vale . --output=JSON
Expected behaviour
The command is unaffected by the dangling symlink.
Actual behaviour
The command fails with
Notes
vale sync
is not affectedThe text was updated successfully, but these errors were encountered: