Closed KazariEX closed 1 month ago
I think rename support can be left out for now. The current class name rename solution is unreliable due to a upstream issue (https://github.com/volarjs/volar.js/issues/176).
This commit treats repeated class declarations as references to the first class, ensuring synchronization when renaming classes with the same name.
This requires ignoring the CSS renaming behavior when using the typescript-semantic renaming feature. Currently, since no interception is implemented, class renaming in the <style>
will be overridden by the CSS functionality. We need to address this issue later.
Since we have extracted the classnames as much as possible, the logic previously used for renaming support is no longer necessary.
commit: 4dd2bd5
``` pnpm add https://pkg.pr.new/vuejs/language-tools/vue-component-meta@4642 ```
``` pnpm add https://pkg.pr.new/vuejs/language-tools/vue-component-type-helpers@4642 ```
``` pnpm add https://pkg.pr.new/vuejs/language-tools/@vue/language-core@4642 ```
``` pnpm add https://pkg.pr.new/vuejs/language-tools/@vue/language-plugin-pug@4642 ```
``` pnpm add https://pkg.pr.new/vuejs/language-tools/@vue/language-server@4642 ```
``` pnpm add https://pkg.pr.new/vuejs/language-tools/@vue/language-service@4642 ```
``` pnpm add https://pkg.pr.new/vuejs/language-tools/vue-tsc@4642 ```
``` pnpm add https://pkg.pr.new/vuejs/language-tools/@vue/typescript-plugin@4642 ```
Awesome, thanks! I tested it manually, it would be great if you could add a test case for it.
I plan to extract this feature to the language service plugin instead of relying on TS virtual code, which will improve the robustness of this feature.
resolve #4641