Closed FelixSchuSi closed 4 years ago
On windows, the quickfixes suggested by the "no-missing-import" rule generate broken paths when dealing with nested folders.
In a project with a structure like this:
parent.ts children └─1 └─folder └─another-folder child1.ts
When you generate an import for child1.ts inside of parent.ts your get this statement:
import "./children\1\folder\another-folder/child1";
This doesnt work since imports require UNIX-like file paths with forward slashes.
This PR fixes the bug. The generated import statement now looks like this:
import "./children/1/folder/another-folder/child1";
Thank you very much for this fix, it looks great!
On windows, the quickfixes suggested by the "no-missing-import" rule generate broken paths when dealing with nested folders.
In a project with a structure like this:
When you generate an import for child1.ts inside of parent.ts your get this statement:
This doesnt work since imports require UNIX-like file paths with forward slashes.
This PR fixes the bug. The generated import statement now looks like this: