You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{
// See https://go.microsoft.com/fwlink/?LinkId=733558
// for the documentation about the tasks.json format
"version": "2.0.0",
"tasks": [
{
"label": "compile",
"type": "shell",
"command": "opam exec -- dune build",
"group": "build",
"problemMatcher": "$ocamlc"
}
]
}
When running the task (Tasks: run task -> compile), my build is launched but the errors are not picked up by vscode.
If I change package.json of this extension to this, then it is able to detect the compilation errors. But only the location. It can't detect the severity or the message.
If I make the `pattern' field a list, even with only one element, then it doesn't seem to work. The documentation says that pattern can be a list. So I don't understand where the problem comes from.
I found out that if I set the error style to short then the problem matcher works. Maybe two matchers are needed. The current one for short errors. And one that ignores the lines starting with \d+ | or \s+\^ for contextual errors.
I'll try to give it a go if you think it's ok to do that.
There is a problem matcher for ocamlc defined in package.json:
vscode-ocaml-platform/package.json
Lines 73 to 94 in 632f4e8
I tried to use it in a project with such a task:
When running the task (
Tasks: run task
->compile
), my build is launched but the errors are not picked up by vscode.If I change package.json of this extension to this, then it is able to detect the compilation errors. But only the location. It can't detect the severity or the message.
If I make the `pattern' field a list, even with only one element, then it doesn't seem to work. The documentation says that pattern can be a list. So I don't understand where the problem comes from.
Another issue but not as critical, the regexp is not able to handle locations for multi-line errors in ocaml 4.09+.
The text was updated successfully, but these errors were encountered: