Totally. Developing against internal APIs is always a pain and it takes a special kind of motivation to keep a project like this alive for as long as he has.

I can understand the core team as well though. Doing what null-ls is kind a nice in principle, but 90% of what people is it for can be done differently without hooking deep into the LSP client like that. I get why they don't want to commit to opening those APIs for what seems to be mostly niche cases.

[–] Paria_Stark@lemmy.world 7 points 1 year ago

Tough news but fair enough from the author.

Let's hope null-ls functionalities can be incorporated deeper into the core nvim lsp.

[–] eat_tar_prog@programming.dev 6 points 1 year ago* (last edited 1 year ago) (2 children)

Sad to hear this as null-ls is a main part of my config. Curious to hear what alternatives are there? I have seen this recommended by some people:

https://github.com/mfussenegger/nvim-lint

[–] tun@lemm.ee 2 points 1 year ago

https://github.com/nvimtools/none-ls.nvim

null-ls.nvim Reloaded, maintained by the community.

[–] ck_@discuss.tchncs.de 1 points 1 year ago

Yeah, I heard good things, I'll probably migrate there soonish.

[–] jeebus@programming.dev 5 points 1 year ago

Bummer. It's a key part of my config.

load more comments