Import path autocomplete with tsconfig path containing "/"

[s4m0r4m4]

TypeScript Version: 4.0.2

Search Terms: import path autocomplete tsconfig path slash duplicate text

Code
tsconfig snippet:

{
   "compilerOptions": {
       "paths": {
            "@myproj/lib-123": ["libs/lib123/index.ts"]
       }
    }
}

Behavior in any typescript file:

// Start typing this and an auto-complete suggestion comes up for "@myproj/lib-123" (yay):
import { xyz } from "@myproj/lib-
// But when I select the autocomplete, it inserts this (oops):
import { xyz } from "@myproj/@myproj/lib-123"

Expected behavior:
import { xyz } from "@myproj/lib-123"

Actual behavior:
import { xyz } from "@myproj/@myproj/lib-123"
If the tsconfig shortcut does not contain a "/" this works just fine

Playground Link: I imagine this is not necessary here, let me know.

Related Issues: None.

[s4m0r4m4]

Hi @RyanCavanaugh, if you point me in the right direction I'd likely be willing to help with this!

[s4m0r4m4]

Another example: if I'm adding //#endregion, typescript gives me the autocomplete while I'm typing, but when I activate the autocomplete, it results in ////#endregion

[s4m0r4m4]

Hi @RyanCavanaugh, just checking in to see if you can point me in the right direction to contribute here. It looks like perhaps https://github.com/microsoft/TypeScript/blob/417b8a94817b7930351eb696470a7583289d91f1/src/services/completions.ts is the right place to start.

[s4m0r4m4]

I can confirm this is still happening in v1.52.1, TypeScript 4.1.2. Looks like it might be resolved in 4.1.3 from the linked PR.

[ShuiRuTian]

You would better test it with latest typescript server built from current master branch.
Usually TS lib update every 3 months. For each subversion after release, TS team only pick several PR .