Open tsmaeder opened 5 months ago
@cdamus @martin-fleck-at
On item 1 I can say that it is a deliberate decision to let plug-in providers offer headless and backend plug-ins in the same package for convenience and clarity of distribution, installation, and update. I'm working on a project that foresees taking advantage of this single-sourcing of both kinds of plug-ins: headless plug-ins contributing application-specific APIs and backend plugins contributing UI that in part delegates to other plug-ins that contribute extensions on those custom APIs.
On item 4 this is one reason why a plugin can optionally use the "theia-headless"
value for the "engine"
property, if it otherwise wouldn't provide a headless entry-point script. I'm not sure myself how useful this is as it introduces issues in VSIX packaging, I think.
Feature Description:
Currently, we deploy back end and headless plugins the same way. This can lead to issues like https://github.com/eclipse-theia/theia/issues/13638. There are a couple of questions open for me: