Test: JS/TS update imports on file move

[mjbvz]

Testing for #49579

• macOS @auchenberg
• linux @ramya-rao-a
• windows @RMacfarlane

Complexity: 1

Summary
VS Code will now attempt to update import paths when you move or rename a js/ts file using the vscode API. This is controlled by the javascript.updateImportsOnFileMove.enabled setting. The default behavior of this setting is to prompt the user for each file rename / move

Note that directory renames are currently not supported. This is tracked by #50244

Testing
In a js/ts project with imports and a tsconfig or jsconfig, try moving and renaming files. Confirm that you are prompted and can automatically update import paths.

Things to try:

• Test different values for javascript.updateImportsOnFileMove.enabled, such as "always" and "never"
• Make sure format style and preferences are respected

[octref]

Was testing another issue and had to tweak the setting, but why have the .enabled in the end when typescript.updateImportsOnFileMove would do?

[tommhuth]

this caused major trouble for me, ending up with all my imports (including node_modules) being mangled into redonk stuff like:

// wtf?
import React from "../../../../../Library/Caches/typescript/2.9/node_modules/@types/react"
// this points directly to my node_modules folder, instead of @scope/shared-react-components/native
import { SplashPosterSubtitle, SplashPoster, SplashPosterTitle } from "../../../../shared-react-components/native"

Should I open a bug for this?

[auchenberg]

@tommhuth Yes please.