Replies: 1 comment
|
This would be a very welcome quality-of-life addition. The reason it currently works only on a per-warning basis comes down to how How VS Code Handles "Fix All in File"In the Language Server Protocol (LSP), batch code actions require the language server to register either:
Right now, the Tailwind language server emits individual "editor.codeActionsOnSave": {
"source.fixAll.tailwind": "explicit"
}Workarounds Available Today for Large CodebasesIf you have many legacy files with dozens of non-canonical warnings:
|
Uh oh!
There was an error while loading. Please reload this page.
I have several codebases made before the VSCode extension started displaying
suggestCanonicalClasseswarnings. Those tend to have a lot of warning like these, and LLMs tend to generate non-canonical classes as well.The extension provide quick fixes for those warnings, but only on a per-warning basis. Common IntelliSense providers like ESLint, TypeScript, etc provide quick fix actions to apply all fixes available for a given warning type in a file.
It would be a nice QoL feature to have.
All reactions