Age | Commit message (Collapse) | Author | |
---|---|---|---|
2020-08-07 | Fix #2907 - Handle dictionaries for capabilities | w0rp | |
2019-09-12 | Add ALERename (tsserver & LSP), ALEOrganizeImports (tsserver) and auto ↵ | Jerko Steiner | |
import support (tsserver) (#2709) This commit adds support for renaming symbols in tsserver and with LSP tools, and for organising imports with tsserver. Completion results for symbols that can be imported are now suggested if enabled for tsserver completion done via ALE. | |||
2019-02-15 | #2295 Send an empty object for the initialized notification, per the spec | w0rp | |
2019-02-15 | Fix #2295 - Respond to initialize with an initialized message | w0rp | |
2019-02-13 | #2132 Use an on-init callback for all LSP logic | w0rp | |
2018-10-31 | Merge pull request #2035 from jparise/lsp_config_callback | w0rp | |
Add a `lsp_config_callback` linter option | |||
2018-10-31 | Implement LSP symbol search | w0rp | |
2018-10-31 | Only send LSP config updates when the dict changes | Jon Parise | |
Each LSP connection now stores its configuration dictionary. It is initially empty (`{}`) and is updated each time the LSP connection is started. When a change is detected, the workspace/didChangeConfiguration message is sent to the LSP servers with the updated configuration. | |||
2018-08-24 | Use one LSP connection per project | w0rp | |
2018-08-16 | Fix #1816 - Fix a type error in the initialize message handler | w0rp | |
2018-07-22 | Check LSP capabilities before using them | w0rp | |
2018-07-19 | Capture server capabilities from LSP servers | w0rp | |
2017-07-30 | Cover special LSP initialize response handling with Vader tests | w0rp | |