@ttsc/vscode 0.21.0 → 0.23.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -1
- package/dist/ttsc-vscode-0.23.0.vsix +0 -0
- package/lib/extension.js +13718 -8715
- package/package.json +7 -7
- package/dist/ttsc-vscode-0.21.0.vsix +0 -0
package/README.md
CHANGED
|
@@ -121,7 +121,7 @@ No diagnostics? Work through these in order:
|
|
|
121
121
|
2. Confirm `ttsc` resolves in the project: `npx ttsc --version`.
|
|
122
122
|
3. Confirm the project itself checks: `npx ttsc --noEmit`.
|
|
123
123
|
4. Open **View → Output → ttsc** and read the server log.
|
|
124
|
-
5. For full LSP tracing, set `ttsc.trace.server` to `"verbose"
|
|
124
|
+
5. For full LSP tracing, set `ttsc.trace.server` to `"verbose"`, then run **Developer: Set Log Level...**, select **ttsc (trace)**, and choose **Trace**. Tracing starts immediately; do not reload the window.
|
|
125
125
|
|
|
126
126
|
If diagnostics work but lint completion does not, press Ctrl+Space after `@` inside a JSDoc block. After changing the lint config or project-indexed inputs, save the file: the completion corpus is rediscovered in the background on save. `ttsc: Restart language server` is still needed for a completion trigger character the session never advertised, which the **ttsc** output channel names when it appears.
|
|
127
127
|
|
|
Binary file
|