Skip to content

Fix assertion -- an import may come from a require() call #19667

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

Merged
3 commits merged into from
Nov 7, 2017

Conversation

ghost
Copy link

@ghost ghost commented Nov 1, 2017

Fixes #19629

@ghost ghost requested a review from armanio123 November 1, 2017 20:31
////export const foo = 0;

// @Filename: /b.js
////const a = require("./a");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also add a test for import("./a");

@mhegazy
Copy link
Contributor

mhegazy commented Nov 1, 2017

Please port this to release-2.6

@ghost ghost merged commit 2fcf8b7 into master Nov 7, 2017
@ghost ghost deleted the completionsimport_require branch November 7, 2017 15:41
ghost pushed a commit that referenced this pull request Nov 7, 2017
* Fix assertion -- an import may come from a require() call

* Add test for `import("./a")`
aluanhaddad pushed a commit to aluanhaddad/TypeScript that referenced this pull request Nov 7, 2017
…19667)

* Fix assertion -- an import may come from a require() call

* Add test for `import("./a")`
ghost pushed a commit that referenced this pull request Nov 7, 2017
…19810)

* Fix assertion -- an import may come from a require() call

* Add test for `import("./a")`
@microsoft microsoft locked and limited conversation to collaborators Jun 14, 2018
This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant