Skip to content

Report error if exports or require is used for declaration name in external module #569

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
merged 2 commits into from
Sep 4, 2014

Conversation

sheetalkamat
Copy link
Member

Fixes #63

return;
}

// Uninstantiated modules shouldnt do this check
Copy link
Contributor

Choose a reason for hiding this comment

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

typo: shouldn't

@mhegazy
Copy link
Contributor

mhegazy commented Sep 4, 2014

Please add tests for the negative case, uninstanciated modules, non-top level declarations with export/import and internal modules

👍

@sheetalkamat
Copy link
Member Author

uninstanciated modules already exists in tests\cases\compiler\collisionExportsRequireAndUninstantiatedModule.ts

I will add test cases for non top level declarations

sheetalkamat added a commit that referenced this pull request Sep 4, 2014
Report error if exports or require is used for declaration name in external module
@sheetalkamat sheetalkamat merged commit f582902 into master Sep 4, 2014
@sheetalkamat sheetalkamat deleted the collisions branch September 4, 2014 20:44
@microsoft microsoft locked and limited conversation to collaborators Jun 18, 2018
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.

[Errors] top level identifier named require or exports
2 participants