Imports auto-update replaces relative path with alias-path

[wclr]

• I've renamed file ChartWheel.ts -> ChartWheel2.ts
• Vscode/ts updated import relative paths like ./ChartWheel -> ~/client/cycles/ChartArea/ChartWheel2
• I would expect ./ChartWheel -> ./ChartWheel2
  tsconfig compiler options have following config for paths:

   "baseUrl": ".",
    "paths": {
      "~/*": ["./apps/*"],
    }

So is it possible for vscode/ts to keep existing import path "style" the same while updating imports?

btw is it more correct to create issues on auto-import in TS repo?

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• Support path alias Rename import path (#60918)

[mjbvz]

Try setting "typescript.preferences.importModuleSpecifier": "relative". This should make ts prefer using relative paths for quick fixes and auto imports (although we will continue to understand both paths styles)

@Andy-MS By default do we prefer using paths over relative paths?

As of #25803 we should prefer the relative path when it's shorter, so I would consider this a bug. I can't reproduce this problem in a simple project containing just apps/client/cycles/ChartArea/user.ts and apps/client/cycles/ChartArea/ChartWheel.ts and the compiler options posted above.

@whitecolor It would help if you could provide a specific repro for this. The only things that should matter are the path of the importing file, the path of the imported file, the tsconfig.json, and the operating system you're using. Also be sure you're testing with typescript@next (set up instructions for vscode). It should not be necessary to set typescript.preferences.importModuleSpecifier, we should prefer the relative path in this case by default.