Allow importModuleSpecifier: "relative" to be overridden for explicitly configured "paths" in a jsconfig/tsconfig

This is a follow-up issue of https://github.com/microsoft/TypeScript/issues/40139

As per the docs, once you've imported a variable somewhere, vscode knows where to find it (bypassing the issue above).

I want all my code to be imported with relative imports everywhere for consistency. so I set "javascript.preferences.importModuleSpecifier": "relative". However, I don't want relative paths to be used when importing from a module declared in tsconfig's paths, as I specifically put it there so it can be resolved as an absolute import for convenience.

Clearly these 2 settings are conflicting, but I wonder if the current compromise is the best one (i.e. settings.json wins over tsconfig)?

I would expect to be able to auto-import variables from my paths module absolutely, even though I want everything else to import relatively.

• VSCode Version: Insiders
• OS Version: macOS 10.15.6

Steps to Reproduce:

1. Clone this repo: https://github.com/Floriferous/paths-resolution
2. Go to branch absolute-import-paths
3. Notice test2.js imports someVar properly
4. Open test.js, try to auto-import someVar, notice intellisense only suggests a relative import

Does this issue occur when all extensions are disabled?: Yes

まずパス解決の再現から始めます。特に test.js、test2.js、および参照されている jsconfig/tsconfig の paths 設定を確認し、相対パス優先を有効にした状態で auto-import の候補を再現してください。明示的に設定されたパスに対する auto-import の処理を追跡してください。paths ベースの import が絶対パスとして提案され、それ以外の import は相対パスのままになれば完了です。