cerxes/babel
3
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Annotate more errors with expected token (#172)

Browse Source 
Expanding on #150, this allows `unexpected()` to accept the expected token type instead of a message string.
This overload is then used in a couple more places (that independently implement a logic similar to `expect()`'s) to construct an `Unexpected token, expected FOO` message.
This commit is contained in:
Moti Zilberman
2016-10-14 23:10:09 +03:00
committed by Henry Zhu
parent 99fbcefa65
commit d3af158ba5
36 changed files with 45 additions and 41 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
test/fixtures/core/uncategorised/388/options.json vendored
View File

@@ -1,3 +1,3 @@
{
"throws": "Unexpected token (1:6)"
"throws": "Unexpected token, expected ; (1:6)"
}

2
test/fixtures/core/uncategorised/389/options.json vendored
View File

@@ -1,3 +1,3 @@
{
"throws": "Unexpected token (1:6)"
"throws": "Unexpected token, expected ; (1:6)"
}

2
test/fixtures/core/uncategorised/405/options.json vendored
View File

@@ -1,3 +1,3 @@
{
"throws": "Unexpected token (1:2)"
"throws": "Unexpected token, expected ; (1:2)"
}

2
test/fixtures/core/uncategorised/407/options.json vendored
View File

@@ -1,3 +1,3 @@
{
"throws": "Unexpected token (1:2)"
"throws": "Unexpected token, expected ; (1:2)"
}

2
test/fixtures/core/uncategorised/408/options.json vendored
View File

@@ -1,3 +1,3 @@
{
"throws": "Unexpected token (1:2)"
"throws": "Unexpected token, expected ; (1:2)"
}