-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Services shows diagnostic when augmenting relative path #20017
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
Comments
@sheetalkamat From the log:
@sheetalkamat Any idea why does |
@Andy-MS I think i figured out the issue.. I think project for a.ts is not yet updated (since background changes are delay updated) when b.ts is opened and we didn't update the graph of the project when we find one when trying to find project of b.ts (i will get the fix in PR soon) It would be interesting to see if you got the file creation event for b.ts (that is before the time your log starts at) or not. If you got that, you should see errors updated as soon as project is updated. If you didn't receive the file creation watcher invoke in the log, then i suspect it could be same as #19989 |
It looks like there is no file creation event.
|
… the existing project Fixes #20017
Yeah that portion is dupe of #19989 |
TypeScript Version: 2.7.0-dev.20171114
Steps
Create
a.ts
and type:Create
b.ts
and type:Expected behavior:
No error.
Actual behavior:
In services, see error:
Invalid module name in augmentation, module './a' cannot be found.
No error on command line.
The text was updated successfully, but these errors were encountered: