Good for him, I personally think null-ls should be a core functionality rather than a plugin.
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.
Tough news but fair enough from the author.
Let’s hope null-ls functionalities can be incorporated deeper into the core nvim lsp.
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/nvimtools/none-ls.nvim
null-ls.nvim Reloaded, maintained by the community.
Yeah, I heard good things, I’ll probably migrate there soonish.
Bummer. It’s a key part of my config.
