Skip to content

Fix assertion: class reference location may be 'default' keyword instead of class name #21630

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.

Sign up for GitHub

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

Jump to bottom
Merged
2 commits merged into from
Feb 5, 2018
Merged

Fix assertion: class reference location may be 'default' keyword instead of class name #21630

2 commits merged into from
Feb 5, 2018

Conversation

ghost
Copy link

@ghost ghost commented Feb 5, 2018

Fixes #21594

@ghost ghost requested a review from armanio123 February 5, 2018 16:51
armanio123
armanio123 approved these changes Feb 5, 2018
View reviewed changes
Copy link
Contributor

@armanio123 armanio123 left a comment

Choose a reason for hiding this comment

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

Looks good, just check the build failures.

@ghost ghost merged commit d584f4d into master Feb 5, 2018
@ghost ghost deleted the findAllRefsExportDefaultClassConstructor branch February 5, 2018 21:24
@microsoft microsoft locked and limited conversation to collaborators Jul 3, 2018
This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@sheetalkamat @armanio123