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
Currently a RenameProvider can be instructed to make renames that are not valid, eg.:
import"dart:html";
Here, you can rename on the import which makes no sense. While it's possible for us to return no edits, it's weird to give the user a textbox pre-populated with import.
It would be better if a RenameProvider can be queried to see whether a rename is valid for a given location and Code can then avoid showing the rename box entirely.
The text was updated successfully, but these errors were encountered:
Currently a RenameProvider can be instructed to make renames that are not valid, eg.:
Here, you can rename on the
import
which makes no sense. While it's possible for us to return no edits, it's weird to give the user a textbox pre-populated withimport
.It would be better if a RenameProvider can be queried to see whether a rename is valid for a given location and Code can then avoid showing the rename box entirely.
The text was updated successfully, but these errors were encountered: