-
Notifications
You must be signed in to change notification settings - Fork 324
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
why is the exlint:source-code-fxer shouldFix parameter false #1846
Comments
rolling back |
You can pass options to the linter using |
Let me know how it goes. |
@dbaeumer can this option be set in the eslint.config.js file? It seems like VsCode autosets the "source.fixAll.eslint" to "explicit" now, as it doesn't support boolean values anymore. |
@Derasm yes that is correct. But the extension / VS Code handles them equally so things should work the same way. Do you see it not working with the |
The options literal passed to the linter is the one from |
I am using eslint v8.57.0 and I use
eslint-config-prettier
with my prettier rules in my eslint config.I have pasted my eslint settings from my vscode settings at the end of this post.
Formatting on save has suddenly stopped working and I have no idea why.
I did notice this entry in the eslint output of vscode.
I can see this in the eslint source code here.
And it appears to be an option that is somehow passed in as option here.
Can I set this value on the extension so that it starts formatting on save again?
The text was updated successfully, but these errors were encountered: