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

load_launchjs is deprecated, how are we supposed to load configurations? #1430

Closed
00sapo opened this issue Jan 20, 2025 · 3 comments
Closed

Comments

@00sapo
Copy link

00sapo commented Jan 20, 2025

Problem Statement

Recently, the function load_launchjs has been deprecated. However, it's not clear to me which other function should replace it.

This is an example of config I have that relies on it:
Image

Possible Solutions

No response

Considered Alternatives

No response

@mfussenegger
Copy link
Owner

You generally shouldn't have to load them manually anymore. See https://github.com/mfussenegger/nvim-dap/releases/tag/0.9.0

In particular also #1237

Custom file names are no longer supported in the same way because they counter the motivation of going with the vscode format to be able to share the configurations between nvim & vscode users.

They'd still be a way to make that work via a custom provider but I don't recommend it

@00sapo
Copy link
Author

00sapo commented Jan 20, 2025

Is the Json file reload when it changes? Also, I just don't like having the same configuration for vscode and neovim because they are simply incompatible (vscode assumes some parameters as default). Moreover, having a folder named .vscode doesn't make sense to me (but I understand that this is not a concern for most people). Maybe just giving the option for the default file name to be loaded would be enough?

@mfussenegger
Copy link
Owner

Is the Json file reload when it changes?

It's always read on demand, which has the advantage that removal of config entries now also works.

Maybe just giving the option for the default file name to be loaded would be enough?

Not going to add that, you'll have to add a custom provider.

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

2 participants