This repository was archived by the owner on May 19, 2018. It is now read-only.
Fix flow type-parameter-declaration test with unintended semantic#361
Merged
danez merged 1 commit intobabel:masterfrom Feb 22, 2017
Merged
Fix flow type-parameter-declaration test with unintended semantic#361danez merged 1 commit intobabel:masterfrom
danez merged 1 commit intobabel:masterfrom
Conversation
Codecov Report
@@ Coverage Diff @@
## master #361 +/- ##
========================================
Coverage ? 97.8%
========================================
Files ? 21
Lines ? 3504
Branches ? 925
========================================
Hits ? 3427
Misses ? 29
Partials ? 48Continue to review full report at Codecov.
|
danez
approved these changes
Feb 22, 2017
Member
|
Thank you |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This spec compiled to CallExpressions due to ASI failure. I assumed this was unintentional and added semicolons, resulting in a presumably more intentional semantic.