Relative paths no longer working

My paths are no longer relative to my current folder since either the 2.6.1 or 2.7.0 update.

I used to be able to do './' and the suggestion would be from my current folder. However it now always suggests from the workspace root folder. All of my settings are default.

[ChristianKohler]

Ok. I found the issue.

Analysis

By default, PathIntellisense reads the baseUrl in the tsconfig.

For example, if the tsconfig looks like this:

 {
 	"baseUrl": "src",
 }

“src” would we used as a key to ${workspace}/src

{
	import {} from 'src/mymodule';
}

With Angular, the baseUrl is set to:

 {
 	"baseUrl": "./",
 }

which means that the “key” is ./ which would then be resolved to ${workspace}/./

The root of the problem is my over simplified solution to how I resolve the baseurl. I only add the baseurl to the mapping list like this:

 {
 	key: "src",
        value: "${workspaceRoot}/src"
 }

Now when you type "src/", the mapping resolved to "${workspaceRoot}/src" showing you all the children of src.

That approach works with all baseUrls, except ./ (afaik).

Short term solution

Just disable the baseUrl support.

Long term solution

Not sure yet. I’d either have to rewrite the baseUrl logic to deal with ./ or just ignore it. Not sure.

Thank you all for you inputs. Hope disabling the baseUrl support work for you for now.

[spfuller]

Thanks so much for this release. I can confirm that the issue is fixed with this new version.