Prototype update import paths on file rename/move for JS/TS #50074
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@jrieken and @alexandrudima I'm merging this prototype with the understanding that the proposed VS Code api component is not complete. I'd like to schedule getting a proper rename file handler API for next iteration |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#19439
Adds a prototype that updates import paths when you rename or move a js/ts file. This is accomplished by introducing a new proposed VS Code API for understanding when a resource has been renamed or rename (we don't try detecting renames/moves that happen outside of vscode). The new proposed API is rough and needs more thought, see #43768
TODO:
setTimeoutand replace with proper handler for when TS opens file.