Hi,
Great to see that BlueOcean is finally going to get some extensibility.
I was waiting for it since Beta, and it was blocker for BlueOcean adoption in some of my projects.
JEP-204 looks good to me. Few questions there:
- What is the reason to create a new extension engine/store? I'd guess there are many existing engines for JS/TS
- There is no logic to unregister extensions. IIUC it means that I may need to reload BlueOcean page if the master restarts and uninstalls some plugins
- Does BlueOcean project plan switch to TypeScript? Or is it just a quick reference implementation?
Sorry if I ask stupid questions, I am not a JavaScript guy.
JEP-203... Would it be possible to clarify the specification in JEP-203?
From what I see it's a top-level document which defines the extensibility goals and announces breaking changes in existing APIs.
Without links to downstream JEPs describing particular sections, IMHO there is no much value in this JEP. And I doubt it can be accepted in the current state until there are specifications for all sections in the document (in downstream JEPs?).
Best regards,
Oleg