-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
Update paths on move misses update when moving file back and forth #24547
Comments
I can't reproduce the error if I open I can reproduce this if I don't open any files but do move I suspect the reproducability of this bug has to do with what files are open at the time of the move. Could you write down exactly what files are open when do the move? For me, |
@mjbvz the editor needs to make sure a file is open before it is moved. there are cases where we have no way of knowing the context of the file, e.g. if it was never opened. |
@andy-ms Try closing We currently do this on rename:
I've confirmed in the logs that the old file was opened before the rename started. Should we be firing the |
@sheetalkamat If everything's working correctly, there should never be an inferred project at all because |
…rror checking When file is moved using getEditsForFileRename, the watch notification could be delayed This could result in project updates in background that could be delayed and result in file not present in the project after its synchronised Fixes #24547
…rror checking When file is moved using getEditsForFileRename, the watch notification could be delayed This could result in project updates in background that could be delayed and result in file not present in the project after its synchronised Fixes #24547
microsoft/vscode#50811
TypeScript Version: 2.9.1
Search Terms:
Code
jsconfig.json
a.js
:b.js
:a.js
into a sub folder. Select to update paths.a.js
back into top level folderBug:
Sometimes you do not get prompted to update paths. This happens when
getEditsForFileRename
returns no editsHere are the logs:
tsserver.log
It looks like sometimes
a.js
ends up in the inferred project instead of thejsconfig.json
project:The text was updated successfully, but these errors were encountered: