Coordination on testing vscode extensions and fixing problems

Hi folks, I was made aware of https://github.com/theia-ide/theia/issues/3815 today. We are currently working on the following extensions: vscode-java, node-debug (2), xml, vscode-yaml, xml, vscjava.vscode-java-debug and typescript.

We have identified a list of problems in the vscode API implementation inside Theia:

Code lens feature doesn’t work correctly theia-ide/theia#3946

Implement onWillSaveTextDocument event theia-ide/theia#4009

Progress bar doesn’t work correctly with plugins theia-ide/theia#4027

Go to definition doesn’t work theia-ide/theia#4044

Register setContext command theia-ide/theia#4053

workspace/didChangeConfiguration not sending correct params to YAML language server when deployed by plugin ID theia-ide/theia#3892

Commands API is not implemented clearly theia-ide/theia#3968

Add Theia Plugin APIs to support VS Code XML Tooling #11775

Apply code action does not work theia-ide/theia#4081

I would really like to prevent us doing work twice. What is the idea of the with https://github.com/theia-ide/theia/issues/3815 ? Should we collect API issues there?

[original thread by Thomas Mäder]

The epic issue is https://github.com/theia-ide/theia/issues/3956

Migrate exiting Theia clients to VS Code extensions

Should we collect API issues there?

I usually go through issues first if something does not work

My team is addressing these issues in the next 3 weeks:

workspace/didChangeConfiguration not sending correct params to YAML language server when deployed by plugin ID theia-ide/theia#3892
Add Theia Plugin APIs to support VS Code XML Tooling #11775
Code lens feature doesn’t work correctly theia-ide/theia#3946
Go to definition doesn’t work theia-ide/theia#4044