-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vim.validate is deprecated. Feature will be removed in Nvim 1.0 #3583
Labels
bug
Something isn't working
Comments
Right, this is the output from |
I just spotted because the majority of my checkhealth is generated by this deprecation as I have various LSP plugins. |
dundargoc
added a commit
to dundargoc/nvim-lspconfig
that referenced
this issue
Jan 23, 2025
This is because using the old syntax for vim.validate causes `:checkhealth vim.deprecated` to be flooded with deprecated messages. It would also be possible to do a version check and use the newer syntax for vim.validate, but since configs.lua will be replaced by vim.lsp.config in the future there is little need to future-proof it. Closes neovim#3583.
dundargoc
added a commit
to dundargoc/nvim-lspconfig
that referenced
this issue
Jan 23, 2025
This is because using the old syntax for vim.validate causes `:checkhealth vim.deprecated` to be flooded with deprecated messages. It would also be possible to do a version check and use the newer syntax for vim.validate, but since configs.lua will be replaced by vim.lsp.config in the future there is little need to future-proof it. Closes neovim#3583.
dundargoc
added a commit
that referenced
this issue
Jan 23, 2025
This is because using the old syntax for vim.validate causes `:checkhealth vim.deprecated` to be flooded with deprecated messages. It would also be possible to do a version check and use the newer syntax for vim.validate, but since configs.lua will be replaced by vim.lsp.config in the future there is little need to future-proof it. Closes #3583.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The text was updated successfully, but these errors were encountered: