Skip to content

Clarify code checking for UMD exports... #9897

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
Sep 14, 2016
Merged

Clarify code checking for UMD exports... #9897

3 commits merged into from
Sep 14, 2016

Conversation

ghost
Copy link

@ghost ghost commented Jul 22, 2016

…and eagerly return undefined rather than continuing on to the for loop.

…rather than continuing on to the for loop.
@@ -17713,14 +17713,17 @@ namespace ts {
const parentSymbol = getParentOfSymbol(symbol);
if (parentSymbol) {
if (parentSymbol.flags & SymbolFlags.ValueModule && parentSymbol.valueDeclaration.kind === SyntaxKind.SourceFile) {
const symbolFile = <SourceFile> parentSymbol.valueDeclaration;
Copy link
Member

@DanielRosenwasser DanielRosenwasser Jul 22, 2016

Choose a reason for hiding this comment

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

No space after type assertions (@weswigham can you write this rule? 😄 )

Copy link
Member

Choose a reason for hiding this comment

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

I could. ;)

@ghost ghost assigned yuit Sep 13, 2016
@mhegazy
Copy link
Contributor

mhegazy commented Sep 13, 2016

👍

@ghost ghost merged commit f00d3fc into master Sep 14, 2016
@ghost ghost deleted the umd_export branch September 14, 2016 13:25
@microsoft microsoft locked and limited conversation to collaborators Jun 19, 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.

5 participants