@@ -19,6 +19,8 @@ dynamically tells the char count.
19
19
20
20
* LSP Spec: [ Hover] ( https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_hover )
21
21
* Invocation: ` :lua vim.lsp.buf.hover() `
22
+ * Demo:
23
+ <img src =" ./assets/hover.mov " width =700 >
22
24
23
25
### 2. Go To Definition
24
26
This takes to the definition of the function / method(it is different from
@@ -28,27 +30,36 @@ above where the cursor is at the moment.
28
30
29
31
* LSP Spec: [ Go To Definition] ( https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_definition )
30
32
* Invocation: ` :lua vim.lsp.buf.definition() `
33
+ * Demo:
34
+ <img src =" ./assets/definition_jumps.mov " width =700 >
31
35
32
36
### 3. Code Actions
33
37
When there are errors in your project and editor shows options to fix them,
34
38
these are the code actions. The server returns with the possible potential
35
39
solutions to the problems in the current context. This implementation takes it
36
40
quite seriously xD.
37
41
42
+
38
43
* LSP Spec: [ Code Actions] ( https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_codeAction )
39
44
* Invocation: ` :lua vim.lsp.buf.code_action() ` _ or_ ` :Telescope diagnostics `
45
+ * Demo:
46
+ <img src =" ./assets/code_actions.mov " width =700 >
40
47
41
48
### 4. Completions
42
49
These are simply the suggestions which appear as you type. This implementation
43
50
provides a couple of suggestions based on typing.
44
51
45
52
* LSP Spec: [ Completion] ( https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_completion )
46
53
* Invocation: ` :lua vim.lsp.buf.completion() `
54
+ * Demo:
55
+ <img src =" ./assets/completions.mov " width =700 >
47
56
48
- ### 4 . Diagnostics (Notification)
57
+ ### 5 . Diagnostics (Notification)
49
58
These are simply the errors, warnings, hints along with some more info related
50
59
to them that editor keeps generating async-ly and shows them in the top right
51
60
section (usually). This implementation takes a few funny takes on editors.
52
61
53
62
* LSP Spec: [ Diagnostics] ( https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_publishDiagnostics )
54
63
* Invocation: ` :lua vim.lsp.diagnostic.get_line_diagnostics() ` (these btw get generated in insert mode only)
64
+ * Demo:
65
+ <img src =" ./assets/diagnostics.mov " width =700 >
0 commit comments