-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Code editing sequence matters for typing acquisition #11744
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
I've tried step 9 with a minor modification - use different source file import * as c from "node-calendar";
c.
var calendar = require('node-calendar');
calendar. After adding entry to |
at glance this is a consequence of this change - |
I cannot repro this issue using Ubuntu 16.04.1 LTS, TS: 2.0.6-insiders.20161017, VSCode 1.7.0 insider. |
#11752 is filed to track issue with missing completions after |
This is a different issue, will send a PR with a fix |
OS Version: macOS
TypeScript Version: typescript@^2.0.6-insiders.20161014 using vscode 1.7 insiders
Note:
"typescript.experimentalAutomaticTypeAcquisition": true
must be in your vscode user settings.Steps to Reproduce
~/Library/Application Support/Microsoft/TypeScript/node_modules/@types
package.json
test.js
test.js
in editorpackage.json
in the editortest.js
calendar.
and invoke intellisense using Cmd+SpaceExpected behavior:
Intellisense proposals for the
node-calendar
module are presentedActual behavior:
No
node-calendar
specific proposals are shown.~/Library/Application Support/Microsoft/TypeScript/node_modules/@types
remains unchanged.-> Intellisense proposals for the
node-calendar
module are presentedNote: When first adding the dependency for
node-calendar
inpackage.json
and then adding the require intest.js
auto acquisition and intellisense work as expected.The text was updated successfully, but these errors were encountered: