has anyone got this thing working in neovim?

[jb49088]

mason-lspconfig does not recognize django-template-lsp which is fine, ill just manually install from mason. but then it refuses to attach to htmldjango filetypes anyways

[jb49088]

ok i've got it to attach that was a misconfiguration on my part but mason-lspconfig still does not recognize django-template-lsp. related issue

[oathlesss]

I will look into this! I do not use mason so that might be the problem. I will get back to you with an answer!

[mfxa]

I have this added in my mason config:

vim.lsp.enable('djlsp'),

in my opts block...which likely requires a fairly recent version of neovim. Before that I manually had to call setup for it, I think:

require "lspconfig".djlsp.setup {}

My main problem is that I'm not sure there's a good way to configure djlsp per project, with different django_settings_module, docker_compose_file and docker_compose_service names for each of them.
I think maybe for Helix and vscode people can put settings for djlsp in a config file inside projects themselves and thus have different values that way?

Also - going off a tangent - I think djlsp should support looking for compose.yaml by default as well, because that's the canonical name for it now.

Edit: But normally I do not have to run vim.lsp.enable for LSP's manually, so seemingly there is a bug somewhere making that necessary to do explicitly.

[mfxa]

So yeah, right now I see this message a lot:

LSP[djlsp][Info] Failed to collect project-specific Django data. Falling back to default Django completions.

Not sure if it can be disabled.

[oathlesss]

I agree that we should also support looking for a compose.yaml by default. I will update this later this week!

[oathlesss]

Small status update: I have not found the time yet to look into this issue, I suspect I will have some free time to look into this later this week.

[mfxa]

Thank you!