New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix silent fail for UNC path files on Windows #3045
Comments
Thanks for the report and for using the template. We'll not add this feature as downloading files over a network is out of scope for linting software. |
@hudochenkov Thanks for response, but seems like there is some misunderstanding. |
What you initially described is running Why remote file isn't linted in an editor via editor plugin is a different story. There might be a problem with a way how editor plugin run linter and pass a code and options to it. Try to ask in your editor plugin repository. |
It does. Just check. Eslint CLI supports UNC Paths. Working with network shares in MS Windows using UNC Paths should be 'transparent', so files don't need to be downloaded first.
I'm using SublimeLinter-contrib-stylelint. I guess it just executes stylelint and passes file path as an argument. |
I'll reopen this issue, maybe other maintainers have thoughts about this. I can't test anything on Windows. Can't help more for now. |
It does sound like there's a bug. @plakhin Are you familiar with UNC paths and network shares? Would you be able to investigate further into the code base as I believe most of the stylelint contributors have limited access to the windows machines? |
@jeddy3 I'll try to help, of course, but I'm not very good with node.js. |
Yikes. That's very much a bug and not the intended behaviour. We even have a |
And as soon as it will be resolved the bug with UNC Paths will become more understandable. |
This issue is older than one month. Please ask before opening a pull request, as it may no longer be relevant. |
I cannot reproduce either but |
stylelint doesn't work with network file paths e.g.
stylelint \\192.168.0.1\httpdocs\public\css\
,local file paths e.g.
stylelint c:\httpdocs\public\css\
work fine.any
8.3.1
CLI with
stylelint \\192.168.0.1\httpdocs\public\css\
No
The same as with local file.
No errors or warnings, no output at all, the same as if I run
stylelint c:\httpdocs\public\css\nonexistent.css
The text was updated successfully, but these errors were encountered: