summaryrefslogtreecommitdiff
path: root/test/lsp/test_other_initialize_message_handling.vader
AgeCommit message (Collapse)Author
2020-08-07Fix #2907 - Handle dictionaries for capabilitiesw0rp
2019-09-12Add 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 specw0rp
2019-02-15Fix #2295 - Respond to initialize with an initialized messagew0rp
2019-02-13#2132 Use an on-init callback for all LSP logicw0rp
2018-10-31Merge pull request #2035 from jparise/lsp_config_callbackw0rp
Add a `lsp_config_callback` linter option
2018-10-31Implement LSP symbol searchw0rp
2018-10-31Only send LSP config updates when the dict changesJon 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-24Use one LSP connection per projectw0rp
2018-08-16Fix #1816 - Fix a type error in the initialize message handlerw0rp
2018-07-22Check LSP capabilities before using themw0rp
2018-07-19Capture server capabilities from LSP serversw0rp
2017-07-30Cover special LSP initialize response handling with Vader testsw0rp