You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/lsp.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,6 +25,7 @@ sequenceDiagram
25
25
```
26
26
27
27
## Language Server Debugging
28
+
28
29
If you want to connect a local version of language-servers to aws-toolkit-vscode, follow these steps:
29
30
30
31
1. Clone https://github.com/aws/language-servers.git and set it up in the same workspace as this project by cmd+shift+p and "add folder to workspace" and selecting the language-servers folder that you just cloned. Your VS code folder structure should look like below.
@@ -57,13 +58,16 @@ If you want to connect a local version of language-servers to aws-toolkit-vscode
57
58
6. (Optional): Enable `"amazonq.trace.server": "on"` or `"amazonq.trace.server": "verbose"` in your VSCode settings to view detailed log messages sent to/from the language server. These log messages will show up in the "Amazon Q Language Server" output channel
58
59
59
60
### Breakpoints Work-Around
61
+
60
62
If the breakpoints in your language-servers project remain greyed out and do not trigger when you run `Launch LSP with Debugging`, your debugger may be attaching to the language server before it has launched. You can follow the work-around below to avoid this problem. If anyone fixes this issue, please remove this section.
63
+
61
64
1. Set your breakpoints and click `Launch LSP with Debugging`
62
65
2. Once the debugging session has started, click `Launch LSP with Debugging` again, then `Cancel` on any pop-ups that appear
63
66
3. On the debug panel, click `Attach to Language Server (amazonq)` next to the red stop button
64
67
4. Click `Launch LSP with Debugging` again, then `Cancel` on any pop-ups that appear
65
68
66
69
## Language Server Runtimes Debugging
70
+
67
71
If you want to connect a local version of language-server-runtimes to aws-toolkit-vscode, follow these steps:
68
72
69
73
1. Clone https://github.com/aws/language-server-runtimes.git and set it up in the same workspace as this project by cmd+shift+p and "add folder to workspace" and selecting the language-server-runtimes folder that you just cloned. Your VS code folder structure should look like below.
@@ -75,6 +79,7 @@ If you want to connect a local version of language-server-runtimes to aws-toolki
75
79
/amazonq
76
80
/language-server-runtimes
77
81
```
82
+
78
83
2. Inside of the language-server-runtimes project run:
0 commit comments