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
The readme mentioned that some of the limitations of this extension are caused by VSCode not exposing the AST.
That makes sense. To get the AST ourselves, we'd either have to get a job at Microsoft, or build Tree-Sitter as a WASM and figure out how to get it working inside a VSCode addon.
Fortunately, someone's already done the latter. It's called owlbear and I am curious as to whether the two addons could tap into each others' communities.
The text was updated successfully, but these errors were encountered:
I don't understand; that looks like they want to use tree-sitter for syntax highlighting? I don't see anything in that issue about exposing the AST to addons.
The readme mentioned that some of the limitations of this extension are caused by VSCode not exposing the AST.
That makes sense. To get the AST ourselves, we'd either have to get a job at Microsoft, or build Tree-Sitter as a WASM and figure out how to get it working inside a VSCode addon.
Fortunately, someone's already done the latter. It's called owlbear and I am curious as to whether the two addons could tap into each others' communities.
The text was updated successfully, but these errors were encountered: