Skip to content

Commit

Permalink
Fix: Have a broader regex for ParseError
Browse files Browse the repository at this point in the history
This allows detecting the ParseErrors originating in layer.conf files.
  • Loading branch information
deribaucourt committed Nov 8, 2023
1 parent f301445 commit 65789f2
Showing 1 changed file with 4 additions and 5 deletions.
9 changes: 4 additions & 5 deletions client/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -137,11 +137,10 @@
"${cwd}"
],
"pattern": {
"regexp": "^Parsing recipes...(ERROR): ParseError (at|in) (.+?):(\\d+)?:? (.+)$",
"file": 3,
"line": 4,
"severity": 1,
"message": 5
"regexp": "^.*ParseError (at|in) (.+?):(\\d+)?:? (.+)$",
"file": 2,
"line": 3,
"message": 4
}
},
{
Expand Down

0 comments on commit 65789f2

Please sign in to comment.