vscode: Imports are not updated if multiple files are moved

@9at8 It’s been a year so I guess I’ll ask again: How’s that rebase coming along?

This affects me so often, I wonder why so few people seem to be hitting this.

I can rebase the PR within the next week 😃

How’s that rebase coming along?

I’ve opened a PR to address this issue. If I am unable to get this PR approved, I’ll see if it’s possible to fix this issue via an extension.

This would be great to have implemented or maybe some warning / preventive action. I did end up thinking that around 30 files were updated after changing directory because the prompt did appear and I assumed it was for all files.

Even when a single file is moved, It’s not updating imports in all occurrences. Looks like it’s updating only the first occurrence it finds.

The PR was approved and the fix is now usable in the VSCode Insiders Build

Running into this all the time. As a workaround I (try to remember to) move files one at a time.

I can rebase the PR within the next week 😃

Please, help!! I’m moving 844 test files and everything seems to break every time I do so… Is it just me??

Edit: to tell you the truth, imports are not updated not even when when I move a single folder with just few files.

Yeah, it completely doesn’t work for folders. Sometimes, it works if you move an individual file, but if you do several files in a row, you have to wait for everything to update after each file is moved before moving onto the next file, or it will break. It’s almost worse than the feature not existing. I often wonder how something this broken ever made it into a production build.

I can’t wrap my head around how the maintainers of this can’t give it priority.

It’s because only 14 people have voted for this issue (as of this writing). If hardly anyone is bothered by a bug, the bug won’t get fixed. I don’t love that everything’s a popularity contest, but I guess there’s no better system 🤷‍♂️

Doing some file restructuring at work this week 😊 So giving this thread (and the devs!) some love ❤️

Still an issue with version 1.79.2. Project in Node.js (relative path for imports). While moving a file, the /tests folder is never updated rearding the imports.

Version: 1.79.2
Commit: 695af097c7bd098fbf017ce3ac85e09bbc5dda06
Date: 2023-06-14T08:59:55.818Z
Electron: 22.5.7
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Linux x64 5.19.0-45-generic

Please, help!! I’m moving 844 test files and everything seems to break every time I do so… Is it just me??

Edit: to tell you the truth, imports are not updated not even when when I move a single folder with just few files.

Just updated vscode hoping this fix would be int there but sadly bug still in VSCode as of June 23 2023 😦

This bug is absolutely ANNOYING and frustrating

I have to re-factor a, not even big, Angular codebase. As the team at the customer was totally new to Angular and made a lot of bad design choices. Now I have to manually go through all the .ts files and check if the imports are right. Because this broken piece of software can’t even properly display where there are errors, if you don’t open every file manually. What a disaster.

I mean, how the fu* is it possible that this editor, which is claimed to be the most versatile IDE, doesn’t even get basic sh* like that right???

Sorry for the language. But I’m forced to use it for UI work at my current project, as I won’t get IntelliJ Ultimate installed by the admins on my assigned dev VM, or any other software better than this as I won’t get root or sudo. Yeah, that’s a whole different story. But it doesn’t change the fact that this is such basic functionality for an IDE that I can’t wrap my head around how the maintainers of this can’t give it priority. It’s so infuriating. Maybe it’s user error,idk,I couldn’t find anything helpful yet. But if it is, this should work out of the box and no thought needed. As it is, a very basic feature. Maybe not simple,but basic.