-
Notifications
You must be signed in to change notification settings - Fork 633
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
lsp: Rename components, structs and enum from places where they are used #7305
Conversation
It mostly works when testing from VSCode, but it still has a couple of rough edges where the tests pass, but VSCode does not want to trigger. I'll poke at it a bit more tomorrow. |
I started to pull out a bit of code from here into easier to review portions in separate PRs... |
9b6416d
to
e517dc8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(partial review)
Nice to see this coming along.
Please make sure there are also tests that control that things that have the same name but are different (eg, a struct and a property) are not renamed.
Apologies is this is already there and I missed it.
e517dc8
to
d7af605
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work!
Good to see this finally done.
I'll do one more round through CI: I seem to have missed a test for renaming a component with an enum of the same name in scope. |
... and their usages and imports/exports Use the token_info to do this.
d7af605
to
aba42fa
Compare
This has pretty decent test coverage, but it is more involved than the first and it is admittedly a bit of a mess in the PR...
I was test driven and forgot to stop along the way ;-)