Conversation
4b1ef25 to
f5624e3
Compare
fe6eef9 to
ded7d77
Compare
f47f877 to
e3781e6
Compare
c1c95d5 to
8f03a7f
Compare
3 tasks
78c8fbb to
eb4c32d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📑 Description
This is pretty far out, but gives a placeholder for future development and shows the progress getting made in the background. This moves entirely to using
vim.lsp.configandvim.lsp.enablefor powering LSP features in Neovim.Required Before Merging
nvim-lspconfigmigration tovim.lsp.config: Missing legacy configs neovim/nvim-lspconfig#3705mason-lspconfigv2 releaseworkspace_requiredoption invim.lsp.configℹ Additional Information
configtable has been refactored to be a general API forvim.lsp.configwhich includes moving default capabilities and flags toconfig = { ["*"] = { capabilities = {}, flags = {} } }, users can still do their configuration in~/.config/nvim/lsp/<server_name>.luaon_attachbehavior is moved to an autocommand onLspAttacheventon_attachfunction extension simply adds onto this autocommand and allows easily modifying it/reverting things that are not desired.mappings/autocommands/commandsoptions are still left and are simply part of the defaulton_attachautocommandcapabilitiesandflagsis simply callingvim.lsp.config("*", { capabilities = M.config.capabilities, flags = M.config.flags })require("astrolsp").lsp_opts(server_name)has been removed. The configuration can simply be retrieved withvim.lsp.config[server_name]mason-lspconfigat runtime. This is not necessary as Mason packages will manage their own mappings tonvim-lspconfigserver names