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
it seems currently tsserver is not able to rename symbols located in vue <script> (or it's me who didn't find how to do it...) Is it possible to rename referenced symbols in vue <script>?
🔍 Search Terms
rename symbol
vue component
List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily and help provide feedback.
✅ Viability Checklist
My suggestion meets these guidelines:
This wouldn't be a breaking change in existing TypeScript/JavaScript code
This wouldn't change the runtime behavior of existing JavaScript code
This could be implemented without emitting different JS based on the types of the expressions
This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
This would have to be on the Vetur side. As someone mentioned in that linked issue, a TypeScript LS plugin would have to communicate the request to the Vue LS. If there is some specific functionality missing from TypeScript that needs to be added to make that work, we’d probably be able to help with that. But from the issue it doesn’t look like anyone has tried it yet.
Suggestion
it seems currently tsserver is not able to rename symbols located in vue <script> (or it's me who didn't find how to do it...) Is it possible to rename referenced symbols in vue <script>?
🔍 Search Terms
List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily and help provide feedback.
✅ Viability Checklist
My suggestion meets these guidelines:
⭐ Suggestion
📃 Motivating Example
considering having a vue typescript project.
src/store/types/getters.ts
src/components/Header.vue
💻 Use Cases
vue typescript project
The text was updated successfully, but these errors were encountered: