Move to new file refactor misses shorthand property referencing import

[mitchellderijcke]

🔎 Search Terms

shorthand property refactor

🕗 Version & Regression Information

• This is the behavior in every version I tried, and I reviewed the FAQ for entries about shorthand properties

⏯ Playground Link

https://www.typescriptlang.org/play/?#code/JYWwDg9gTgLgBAZxtApnAZlCI4CIB0A9EqrgNwBQFhhcAbggMYQAmaAtAHxwBKK6AQ0bIocLnACyEOmmRwAdigDuGYABsUVGpOnB5AczgwAFsAQYArvOHAI8uEvVq4UFDAF6jxtKEiwKKAAefvDoVjZ2cAIAFACUcADeFHApcMzyCBAa+GoQ+tEJJK4AvrGUxVq0UnR6hiZmltYwtvaOas6uINKy3nC+0DABwQONEfYARnGJyanpmdm5+UUoZRQVQA

💻 Code

import store from "./store";

// vscode -> Refactor -> Move to new file

// Moving this function will retain the import
export function a() {
    console.log({store});
}

// Moving this function will remove the import
export function b() {
    console.log(store);
}

🙁 Actual behavior

Import statement is removed when function b is removed.

🙂 Expected behavior

Import statement is retained when function b is removed because it's used by function a.

Additional information about the issue

Happens in vscode and when using LanguageService.getEditsForRefactor.

[RyanCavanaugh]

Closing language service bugs related to the 6.0 implementation. For more information, see #62827