How to launch VSCode Diff when Verify fails?

[X9VoiD]

I've started using Verify just recently, saw this line

and this line

So I expected it to just work with VSCode, however upon failure of tests it doesn't launch any diff within VSCode. Is there some step that I'm missing? Because it's not obvious in the docs for both Verify and DiffEngine if I have to do something extra to make this work.

[SimonCropp]

what is the full path to your VSCode install?

[X9VoiD]

/home/oscar/.nix-profile/bin/code

Though I recommend restructuring the project a bit to be able to optionally search in PATH for the desired executable. (just sniffed around the repo, and saw paths being hardcoded)

[SimonCropp]

search in PATH for the desired executable

happy to accept a PR for that

[X9VoiD]

Just submitted a PR to DiffEngine. Is planning on doing the CLI definitions on a separate PR but if you feel like we should do it on the same PR then please do tell. I hope it is to your satisfaction!

[aalmada]

Hi! I'm new to verify. I'm using vscode on Windows with the code hosted on WSL. Like the original post author, no diff tool appears. What do you suggest to use in this scenario and how to configure it?

[SimonCropp]

@aalmada i dont know. your scenario is not something i have done.