I wish the author thanks and the very best going forward in whatever he chooses to work on.
Having said that, this is going to cause not a little trouble for a lot of Lunarvim users.
I was quite surprised by Lunarvim choosing null-ls as it's default linting and formatting handling plugin.
I had to struggle quite a bit to get null-ls working with the new lvim release because as the author points out, the architecture of the plugin is very much exposed to changes in neovim and lsp.
Spent a lot of time after the lvim 1.3 release to get null-ls working as before. I even tried debugging the lua code a bit to get a sense of what was going wrong. Finally I just ditched it and went with a different linter plugin (and yet another formatter plugin).
Having said that, this is going to cause not a little trouble for a lot of Lunarvim users.
I was quite surprised by Lunarvim choosing null-ls as it's default linting and formatting handling plugin.
I had to struggle quite a bit to get null-ls working with the new lvim release because as the author points out, the architecture of the plugin is very much exposed to changes in neovim and lsp.
Spent a lot of time after the lvim 1.3 release to get null-ls working as before. I even tried debugging the lua code a bit to get a sense of what was going wrong. Finally I just ditched it and went with a different linter plugin (and yet another formatter plugin).