search

noib3 / nvim-completion

:zap: An async autocompletion framework for Neovim
MIT License
503 stars 13 forks source link

Changelog #13

Open ok-nick opened 2 years ago

ok-nick commented 2 years ago

I've been interested in this project and looking back every once in a while to see if there have been any changes. Unfortunately, all I can really do is look at commit messages which is quite tedious. Is there any way you could supply a changelog file to keep track of all the new updates?

noib3 commented 2 years ago

I was thinking of creating a CHANGELOG.md after releasing the first alpha. Right now I'm adding/changing features pretty much every commit, and documenting every change would add significant overhead to the development cycle.

The lsp source (sort of) works, but there are still lots of rough edges and bugs that need to be addressed. If you want to try it out a minimal config is

require("compleet").setup({
  sources = {
    lsp = { enable = true },
  }
})

together with

local lspconfig = require("lspconfig")
local capabilities = require("compleet").lsp_client_capabilities()

-- For every lsp server you have enabled
lspconfig.<server>.setup({
  capabilities = capabilities,
  ...
})

to advertise the client's completion capabilities to lsp servers.

ok-nick commented 2 years ago

The project is still pretty young and I wouldn't expect you to note down everything. However, it would be nice if you could include any major changes to keep everyone updated.