Johnson Chu
Johnson Chu
@yaegassy Are you using @volar-plugins/pretty-ts-errors or building a client plugin based on pretty-ts-errors-lsp?
For `@volar-plugins/pretty-ts-errors`, in VSCode it also needs to set `isTrusted` and `supportHtml` in the language client middleware. I'm not sure if coc supports it. https://github.com/volarjs/volar.js/blob/5ae44d90936045b92ad9debcfb9ae952bb311fb8/packages/vscode/src/index.ts#L27-L28
@yaegassy please update `@volar-plugins/pretty-ts-errors` to 2.0.0-alpha.23-patch.2, it should fixed the logging issue.
See https://github.com/yoavbls/pretty-ts-errors/issues/21#issuecomment-1512932535
Just to clarify...don't expect it, the language server can cut the original error message, but this will also cause extensions like ErrorLens that rely on diagnostic messages to not work,...
I think we don't need to support the new `@vue/typescript`, we are planning to [deprecate it in 2.0](https://github.com/vuejs/language-tools/issues/3402). Keep using `@volar/vue-typescript` 1.6 would be fine for now. On the other...
This is a PR to migrate to @volar/typescript+@vue/language-core: #129
It seem `getScriptSnapshot` giving invalid svelte content. ```svelte {} ```
If you need to debug, you can add breakpoint at `node_modules/@volar/language-core/out/languageContext.js` line 139.
@A5rocks, @so1ve merged, well done! Next we can add highlighting to the target tag of fallthrough attributes.