feat: automatically configure the vscode extension in nvim-dap
#129
Conversation
…upport the defined adapters
|
I had found few for node-js and fixed in LazyVIM: https://github.com/LazyVim/LazyVim/pull/3165/files But if this repo is going to take the responsibility of configuring the vscode extension, it should add these mappings also. ( I may myself raise PR, but not getting time. So, will be good if someone else can take it up ) |
|
Those adapters are not handled by this plugin so it makes no sense for this plugin to add those mappings. It would be up to the user or whatever plugin creates those types to add it to this same structure. |
|
Looking at the LazyVim code, the |
|
@80avin here is a PR on LazyVim that fixes their configuration of vscode types: LazyVim/LazyVim#3556 |
…3556) `mason-nvim-dap.nvim` adds it's own adapter filetype mappings to the vscode extension in `nvim-dap` (as of jay-babu/mason-nvim-dap.nvim#129) This also moves the type mappings for the `pwa-node` and `node` adapters to where they are defined in the typescript pack. Now that the default internal type mappings are configured we can rely on the automatic loading of the `.vscode/launch.json` that `nvim-dap` does
nvim-dapprovides a vscode extension that loads inlaunch.jsonfiles. It has an internal variable for the mappings from adapters to filetypes when loading configurations. This adds automatic support to connect the filetypes to the adapters defined bynvim-dapHere is the variable: https://github.com/mfussenegger/nvim-dap/blob/master/lua/dap/ext/vscode.lua#L6
And here is where they use it: https://github.com/mfussenegger/nvim-dap/blob/master/lua/dap/ext/vscode.lua#L197