VS Code extension gets confused by --allow-eval

[anka-213]

If I put--allow-eval in a .ghcid file and run the VS Code extension (with the "Run Ghcid" command), it will report all of the evaluated output as problems in the file "/".

[anka-213]

It's not a major issue, I could just run ghcid --allow-eval in a normal terminal inside vs-code instead.

[ndmitchell]

I don't really use the plugin much anymore (I've mostly moved on to Ghcide - https://github.com/digital-asset/ghcide), and I've never used --allow-eval. Happy to take a patch - it's probably a matter of adjusting a regex in the Javascript code - but unlikely to tackle it myself.