Add mason_lspconfig default_handlers #43
Open
Conversation
This file contains 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
Fix an error that was being caused because setup_handlers was being called from nvim-lspconfig instead of mason-lspconfig
MuhammadcodR
approved these changes
Oct 1, 2023
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.
About
Add mason_lspconfig default_handlers instead of traditional nvim-lspconfig setup for each language.
Benefits
This will make you have a default handler when you install a new language server, making it unecessary to setup a new nvim-lspconfig for each new language server that don't require a custom setup. You can still customize new language servers setup, passing a function to it's name's property in the setup_handlers argument table.