Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DAP support #12

Open
nikita-orca opened this issue Jul 30, 2022 · 2 comments
Open

DAP support #12

nikita-orca opened this issue Jul 30, 2022 · 2 comments

Comments

@nikita-orca
Copy link

No description provided.

@florentcigolotti florentcigolotti mentioned this issue Jul 30, 2022
5 tasks
@florentcigolotti
Copy link

florentcigolotti commented Jul 30, 2022

Hi!

I have been working a bit on a PR to add the support for the dap strategy. I got something that is working for simple Test* and Example* right now.
This is a draft for now, I don't feel confident about the integration in the adapter.build_spec function (if someone have some time to add comments on the PR I will appreciate)

Also right now after a debugging session the status sign is broken, I haven't spend much time on it, I will do when I have spare time!

The user experience is awesome when it works! (thanks a lot for writing this plugin)

folke pushed a commit to LazyVim/LazyVim that referenced this issue Jul 22, 2023
neotest-go does not provide a DAP strategy, and thus you cannot invoke the debugger with require('neotest').run.run({strategy=dap}).

There have been efforts to implement this in nvim-neotest/neotest-go#12 but this seems to have stalled.
You can find the background to this change discussed here: #1107
joshmedeski pushed a commit to joshmedeski/LazyVim that referenced this issue Sep 1, 2023
neotest-go does not provide a DAP strategy, and thus you cannot invoke the debugger with require('neotest').run.run({strategy=dap}).

There have been efforts to implement this in nvim-neotest/neotest-go#12 but this seems to have stalled.
You can find the background to this change discussed here: LazyVim#1107
folke pushed a commit to LazyVim/LazyVim that referenced this issue Jun 23, 2024
## What is this PR for?

This PR switches
[nvim-neotest/neotest-go](https://github.com/nvim-neotest/neotest-go)
for
[fredrikaverpil/neotest-golang](https://github.com/fredrikaverpil/neotest-golang).

## Does this PR fix an existing issue?

Neotest-go comes with some problems which are mitigated in
neotest-golang. A full description/background is available in the
project README, but here are some highlights:

### Neotest-go issues mitigated in neotest-golang

- Test Output in JSON, making it difficult to read:
[neotest-go#52](nvim-neotest/neotest-go#52)
- "Run nearest" runs all tests:
[neotest-go#83](nvim-neotest/neotest-go#83)
- Running test suite doesn't work:
[neotest-go#89](nvim-neotest/neotest-go#89)
- Diagnostics for table tests on the line of failure:
[neotest-go#75](nvim-neotest/neotest-go#75)
- Support for Nested Subtests:
[neotest-go#74](nvim-neotest/neotest-go#74)
- DAP support:
[neotest-go#12](nvim-neotest/neotest-go#12)

### Features

- Supports all [Neotest
usage](https://github.com/nvim-neotest/neotest#usage).
- Integrates with [nvim-dap-go](https://github.com/leoluz/nvim-dap-go)
for debugging of tests using delve.
- Inline diagnostics.
- Works great with
[andythigpen/nvim-coverage](https://github.com/andythigpen/nvim-coverage)
for displaying coverage in the sign column (per-Go package, or per-test
basis).
- Monorepo support (detect, run and debug tests in sub-projects).
- Supports table tests (relies on treesitter AST detection).
- Supports nested test functions.

## Notes

- I'm the author of
[fredrikaverpil/neotest-golang](https://github.com/fredrikaverpil/neotest-golang).


## Checklist

- [x] I've read the
[CONTRIBUTING](https://github.com/LazyVim/LazyVim/blob/main/CONTRIBUTING.md)
guidelines.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants