- Issue created by @lauriii
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
📌 Refactor XB internals to not assume /xb-components returns only SDC-powered XB Components Active introduces some additional structure that will make this much clearer to land.
- Merge request !373#3482393: HTTP API: update /xb-components to specify each `Component`'s `extensionType` → (Open) created by wim leers
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
📌 [PP-1] Add support for Blocks as Components Active is in, rebased.
- 🇫🇮Finland lauriii Finland
Discussed this with @longwave and @jessebaker. We believe the
extension_typekey is too narrow and doesn't account for other needs we have for these. Essentially what we need is information on what is the source of the "component". Potential sources are: Blocks, Theme Components, Module Components, Elements, and JavaScript components. Each of these sources then have categories within itself. Here's a visualization of that:
