Fix accidental fall-through in Flow type parsing.

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

Hide file tree

Showing 3 changed files with 6 additions and 0 deletions.
diff --git a/src/plugins/flow.js b/src/plugins/flow.js
@@ -505,6 +505,8 @@ pp.flowParsePrimaryType = function () {
         node.returnType = this.flowParseType();
 
         return this.finishNode(node, "FunctionTypeAnnotation");
+      } else {
+        this.unexpected();
       }
 
     case tt.parenL:

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)"
+}