Update to Theia 1.60 (Lumino)

[sdirix]

Theia 1.60 will contain the migration from PhosphorJS to Lumino. We need to test all examples whether they continue to work as is.

Known breakage:

• The tree-editor consumes a version of @eclipse-emfcloud/theia-tree-editor which will not work without adaption, see here.

[JonasHelming]

@sdirix I would be in favor of just removing and deprecating the example then, WDYT? there is a new example upcoming as well: #241

[JonasHelming]

@sdirix Is there a migration guide on how to find "for sure" breakages?

[sdirix]

@sdirix I would be in favor of just removing and deprecating the example then, WDYT? there is a new example upcoming as well: #241

Depends on whether there will be an adopted version of the tree editor. It's likely a low effort change for them.

@sdirix Is there a migration guide on how to find "for sure" breakages?

There is no specific guide.

For sure breakages are:

• All imports of @theia/core/shared/@phosphor will break
• All custom CSS referring to phosphor classes, e.g. .p-TabBar, needs to be changed, e.g. to .lm-TabBar.

95% breakages are:

• Non-shared imports of @phosphor will very likely lead to typing issues in the best case and runtime errors in the worst case. They should be adapted too

Potential breakages which can not be found without testing:

• Slight behavior changes of Phosphor vs Lumino which have an effect on adopter code base, e.g. empty menu handling
• Code we adopted in Theia and downstream adopters with deep customizations need to adapt too, for example a new initialize promise of the shell to wait for.

For the generator extensions I don't think we will have issues besides the tree-editor, but let's see.

[JonasHelming]

Tested the new release, works with Lumino: https://github.com/eclipse-theia/generator-theia-extension/releases/tag/v0.1.42