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
This was added in the hex-ci fork in hex-ci/vscode-stylelint-plus@66dbb72?w=1 (linking to a diff with suppressed whitespace as there's a bunch of noisy reformatting in there too), where its option name autoFixOnSave mimics the usage of the current vscode-eslint plugin.
This probably the most desired missing feature of shinnn's original work and was the reason the hex-ci fork exists. It'd be great to have autofixing in extension as it seems like this is about to become the official stylelint extension.
Longer term I note that the eslint plugin is on the cusp of releasing a v2 which changes how it registers autofixing - the autoFixOnSave option will be removed and replaced with a hook into vscode's native editor.codeActionsOnSave option (see its README). Eventually it's probably worth reworking the plugin to mimic how vscode-eslint is architected to allow for this autofixing and to ensure the plugin uses the locally installed version of stylelint if available, but that rework can be punted down the road for a while, and a stopgap autofix would be great.
The text was updated successfully, but these errors were encountered:
This was added in the hex-ci fork in hex-ci/vscode-stylelint-plus@66dbb72?w=1 (linking to a diff with suppressed whitespace as there's a bunch of noisy reformatting in there too), where its option name
autoFixOnSave
mimics the usage of the current vscode-eslint plugin.This probably the most desired missing feature of shinnn's original work and was the reason the hex-ci fork exists. It'd be great to have autofixing in extension as it seems like this is about to become the official stylelint extension.
This would let me update the docs in the prettier vscode plugin to make it recommend this plugin once it gets published.
Longer term I note that the eslint plugin is on the cusp of releasing a v2 which changes how it registers autofixing - the
autoFixOnSave
option will be removed and replaced with a hook into vscode's nativeeditor.codeActionsOnSave
option (see its README). Eventually it's probably worth reworking the plugin to mimic how vscode-eslint is architected to allow for this autofixing and to ensure the plugin uses the locally installed version of stylelint if available, but that rework can be punted down the road for a while, and a stopgap autofix would be great.The text was updated successfully, but these errors were encountered: