You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 16, 2023. It is now read-only.
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?
The text was updated successfully, but these errors were encountered:
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
locallspconfig=require("lspconfig")
localcapabilities=require("compleet").lsp_client_capabilities()
-- For every lsp server you have enabledlspconfig.<server>.setup({
capabilities=capabilities,
...
})
to advertise the client's completion capabilities to lsp servers.
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.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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?
The text was updated successfully, but these errors were encountered: