| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Generating the filetype mappings by accessing `vim.lsp.config` turns out to be a bad idea because:
1) performance
2) some `lsp/` configurations in nvim-lspconfig execute code immediately (see angularls)
3) accessing `vim.lsp.config[server_name]` seems to populate `:checkhealth vim.lsp`
|
| |
|
|
|
|
|
|
| |
This also removes all generated code/docs, including relevant scripts. Mappings are now also dynamically generated
instead of compiled. These changes should reduce churn in this plugin and make it more resilient for external changes in
Mason and/or nvim-lspconfig.
Mappings have been centralized in the registry instead.
|
| |
|
|
|
| |
* chore(workflows): update dependencies
* style: enforce import order
|
| |
|
| |
Closes #106.
|
| | |
|
| |
|
