Support custom adapter config #83

New issue

Closed

opened 2024-04-26 19:28:32 +03:00 by YogiPristiawan · 3 comments

YogiPristiawan commented

2024-04-26 19:28:32 +03:00

(Migrated from github.com)

Hi,

i want to load my custom config bellow

  dap.adapters.custom = {
    type = "server",
    host = "127.0.0.1",
    port = 2345,
  }

but the plugins only support the go adapter type

Hi, i want to load my custom config bellow ``` dap.adapters.custom = { type = "server", host = "127.0.0.1", port = 2345, } ``` but the plugins only support the `go` adapter type

leoluz commented

2024-04-29 03:06:20 +03:00

(Migrated from github.com)

Hi @YogiPristiawan,

This project is mainly a Go extension for the nvim-dap plugin. I am not sure what is the intention with custom adapter. Which use cases are you willing to cover with this proposal?

Hi @YogiPristiawan, This project is mainly a Go extension for the nvim-dap plugin. I am not sure what is the intention with custom adapter. Which use cases are you willing to cover with this proposal?

YogiPristiawan commented

2024-04-29 07:48:17 +03:00

(Migrated from github.com)

Because I have constraints when using the defined go adapters configurations:

I can't use a debugger if my main package is not in the root directory. Therefore, I can't use debug_test.
I want to connect to my running delve instance that runs together with Air. I run my project using Air because I need hot reload for local development, and I also need to load my .env file.

Because I have constraints when using the defined `go` adapters configurations: - I can't use a debugger if my `main` package is not in the root directory. Therefore, I can't use debug_test. - I want to connect to my running `delve` instance that runs together with [Air](https://github.com/cosmtrek/air). I run my project using [Air](https://github.com/cosmtrek/air) because I need hot reload for local development, and I also need to load my `.env` file.

stale[bot] commented

2024-10-28 22:32:17 +03:00

(Migrated from github.com)

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.