This repository has been archived by the owner. It is now read-only.

Fix flow type-parameter-declaration test with unintended semantic #361

Merged
merged 1 commit into from Feb 22, 2017

Conversation

Projects
None yet
2 participants
@rattrayalex
Copy link
Contributor

rattrayalex commented Feb 15, 2017

Q A
Bug fix? yes (test fix)
Breaking change? no
New feature? no
Deprecations? no
Spec compliancy? yes
Tests added/pass? yes
Fixed tickets comma-separated list of tickets fixed by the PR, if any
License MIT

This spec compiled to CallExpressions due to ASI failure. I assumed this was unintentional and added semicolons, resulting in a presumably more intentional semantic.

@codecov

This comment has been minimized.

Copy link

codecov bot commented Feb 15, 2017

Codecov Report

❗️ No coverage uploaded for pull request base (master@57aacea). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master    #361   +/-   ##
========================================
  Coverage          ?   97.8%           
========================================
  Files             ?      21           
  Lines             ?    3504           
  Branches          ?     925           
========================================
  Hits              ?    3427           
  Misses            ?      29           
  Partials          ?      48

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 57aacea...3d5e981. Read the comment docs.

@danez

danez approved these changes Feb 22, 2017

@danez

This comment has been minimized.

Copy link
Member

danez commented Feb 22, 2017

Thank you

@danez danez merged commit fab4ca2 into babel:master Feb 22, 2017

2 of 3 checks passed

codecov/project No report found to compare against
Details
codecov/patch Coverage not affected.
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.