-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
[Bug]: format can't trigger auto fix #485
Comments
|
I think I have the same issue - I try to use the following configurations https://gist.github.com/StfBauer/e33f5dda5545b9adafb030992df42a9e While this perfectly works from the command line, VS Code does nothing. The question is, do I do something wrong, or is it a general issue? Meanwhile, the only option I have is to execute stylelint from the terminal window, which is also fine for me for now. |
You should check here for any errors |
@StfBauer |
@chenzhuo198 None of such things - just checked the user settings not the default vscode settings. btw. first image not loading for me. |
Nope, haven't worked either. |
How did you encounter this bug?
if vscode setting has
{ "files.insertFinalNewline": true }
auto fix can't be trigger.
analyzed the source code find this
and
if has config , will get the cache.
can't to find cofig file for gernerate configoptions
Link to Minimal Reproducible Example
without
Code Snippet
No response
Stylelint Configuration
No response
Extension Configuration
No response
Actual Behaviour
auto fix
Expected Behaviour
can't auto fix
Logs
No response
Stylelint Version
v15.11.0
vscode-stylelint Version
v1.3.0
Node.js Version
v16.14.2
Operating System
windows
Windows Subsystem for Linux
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: