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
Standalone extensions are probably better than the fork approach.
I've looked at the changes, and the main ones are the addition of Session, Deno spawn, serializer, which could have been standalone extensions to work with vscode-deno. I don't really understand why they are integrated.
vscode-deno already provides lsp, so I don't understand why it needs additional support.
The text was updated successfully, but these errors were encountered:
Take a look on this issue for some background on the lsp problem.
Currently the extension is a fork due to the lsp issue.
I would love to see the official lsp updated in its own repo (deno) and the controller and serializer in the official extension repository, but if that were not the case, I would publish the controller and serializer as add-on extensions.
Standalone extensions are probably better than the fork approach.
I've looked at the changes, and the main ones are the addition of Session, Deno spawn, serializer, which could have been standalone extensions to work with vscode-deno. I don't really understand why they are integrated.
vscode-deno already provides lsp, so I don't understand why it needs additional support.
The text was updated successfully, but these errors were encountered: