Debugging setup about neotest HOT 5 CLOSED

Thanks, @rcarriga 👍🏿 I'm pretty sure also that nvim-dap has a recipe for it in there, and it definitely works with https://github.com/ray-x/go.nvim which has a config that works, so someone could grab that I haven't looked into it further though, someone else feel free to pick this up as I'm not working on it, as I haven't got the time (or present need).

from neotest.

It also happens to me with node 👀

from neotest.

@hahuang65 the dap strategy hasn't been built into neotest-go someone needs to make a PR for that since at the moment the argument isn't used and there is no dap config for go. I don't know what that should even look like, so someone who does should contribute that change in that repo

from neotest.

I've added a change to notify users when the adapter doesn't support debugging.

@akinsho FYI this might be useful https://github.com/rcarriga/vim-ultest/wiki/Debugging-Recipes#gotest. At the time of writing that vscode-go didn't emit an error exit code which is why the result parsing is there. I never got delve working but didn't put much time into it

from neotest.

Going to close this as the functionality of notifying users when nvim-dap is not supported is there. Adapter specific issues can be raised in their repos

from neotest.