Fix accidental fall-through in Flow type parsing.

When parsing a primary type, `>` would erroneously be treated like `(`.
babel · Jul 26, 2016 · 2bebe36 · 2bebe36
1 parent 88d7e20
commit 2bebe36
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 0 deletions.
diff --git a/src/plugins/flow.js b/src/plugins/flow.js
@@ -506,6 +506,7 @@ pp.flowParsePrimaryType = function () {
 
         return this.finishNode(node, "FunctionTypeAnnotation");
       }
+      break;
 
     case tt.parenL:
       this.next();

diff --git a/test/fixtures/flow/type-annotations/106/actual.js b/test/fixtures/flow/type-annotations/106/actual.js
@@ -0,0 +1 @@
+var f: >x:int) => string;
diff --git a/test/fixtures/flow/type-annotations/106/options.json b/test/fixtures/flow/type-annotations/106/options.json
@@ -0,0 +1,3 @@
+{
+  "throws": "Unexpected token (1:7)"
+}
-Original file line number
+Diff line change
@@ Expand Up / @@ -506,6 +506,7 @@ pp.flowParsePrimaryType = function () { @@
             return this.finishNode(node, "FunctionTypeAnnotation");
           }
+          break;
         case tt.parenL:
           this.next();
@@ Expand Down @@