Closed ChristianMurphy closed 1 year ago
I recognize a lot of the ideas and troubles mentioned in that blog post. I’ll contact them and see if we can work together. :smile:
Released in vscode-mdx@1.5.0
, @mdx-js/language-server@0.2.0
, @mdx-js/language-service@0.2.0
:tada:
Initial checklist
Problem
There is a fair amount of boilerplate code to integrate MDX, TypeScript, and the language server together. This boilerplate may not be necessary with some abstraction.
Solution
Research Volar https://blog.vuejs.org/posts/volar-a-new-beginning.html Formerly the vue language server, which has now split out it's abstractions for other language servers to use.
The abstractions appear to center around low level details:
We may be able to rebase our server on top of that foundational work.
Alternatives
Volar is new, and may or may not suit vscode-mdx. This is mostly an issue to explore feasibility and practicality of leveraging it. If none of it matches, "we shouldn't use it", is a perfectly valid outcome.
Or a more piecemeal approach of leveraging concepts and reusing some functions could also be taken.