-
Notifications
You must be signed in to change notification settings - Fork 26.2k
fix(language-service): ensure correct paths are passed to typescript #21812
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
8a2b687
to
2338a88
Compare
The 2.6 version of TypeScript's `resolveModuleName` started to require paths passed to be separated by '/' instead of being able to handle '\'. `ngc` and `ng` already do this transformation. Fixes: angular#21811
2338a88
to
a3e1059
Compare
You can preview 8a2b687 at https://pr21812-8a2b687.ngbuilds.io/. |
You can preview 2338a88 at https://pr21812-2338a88.ngbuilds.io/. |
You can preview a3e1059 at https://pr21812-a3e1059.ngbuilds.io/. |
let ngService = createLanguageService(ngHost); | ||
const reflectorHost = new ReflectorHost(() => undefined as any, mockHost, {basePath: '\\app'}); | ||
|
||
spyOn(path, 'join').and.callFake((...args: string[]) => { return path.win32.join(...args); }); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: remove { return
and }
ie (...) => path.win32.join(...)
…ngular#21812) The 2.6 version of TypeScript's `resolveModuleName` started to require paths passed to be separated by '/' instead of being able to handle '\'. `ngc` and `ng` already do this transformation. Fixes: angular#21811 PR Close angular#21812
…ngular#21812) The 2.6 version of TypeScript's `resolveModuleName` started to require paths passed to be separated by '/' instead of being able to handle '\'. `ngc` and `ng` already do this transformation. Fixes: angular#21811 PR Close angular#21812
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: #21811
What is the new behavior?
Language service works correctly on Windows.
Does this PR introduce a breaking change?