@@ -115,6 +115,41 @@ COMPLETION SUPPORT *lspconfig-completion*
115
115
116
116
See | lsp-completion | .
117
117
118
+ ==============================================================================
119
+ Migrate to vim.lsp.config *lspconfig-nvim-0.11*
120
+
121
+ The "framework" part of nvim-lspconfig is DEPRECATED . The "configs" are NOT
122
+ deprecated, but were moved to the lsp/ directory so that | vim.lsp.config() |
123
+ automatically finds them.
124
+
125
+ This means:
126
+ - `require' lspconfig' […]` must NOT be used. Use `vim .lsp .config (…)` instead.
127
+ - The `require' lspconfig' ` quasi-framework will be DELETED, and is not
128
+ supported in Nvim 0.11+.
129
+ - The nvim-lspconfig configs (| lspconfig-all | ) now live in "lsp/" instead of
130
+ "lua/lspconfig/".
131
+ - To use the configs, call `vim .lsp .config (…)` instead of `require' lspconfig' […]` .
132
+
133
+ MIGRATION INSTRUCTIONS
134
+
135
+ To migrate:
136
+ - Upgrade to Nvim 0.11 or later.
137
+ - Change `require' lspconfig' […]` to `vim .lsp .config (…)` .
138
+ - Some field names changed, see | lspconfig-vs-vim.lsp.config | .
139
+ - See | lsp-config | for details.
140
+
141
+ BACKGROUND
142
+
143
+ Since Nvim 0.11, nvim-lspconfig provides configs in its "lsp/" directory. The
144
+ old configs still exist in "lua/lspconfig/configs/" but are deprecated and
145
+ will be DELETED.
146
+
147
+ This means the "configs" role of nvim-lspconfig continues to be relevant, but
148
+ it is now a "data-only" repository instead of a "framework". The only change
149
+ needed from you, and from plugins, is to use the Nvim 0.11 `vim .lsp .config`
150
+ interface to setup LSP configs instead of the old `require' lspconfig' `
151
+ quasi-framework.
152
+
118
153
==============================================================================
119
154
DEBUGGING AND TROUBLESHOOTING *lspconfig-debugging*
120
155
0 commit comments