Refactor XB internals to not assume /xb-components returns only SDC-powered XB Components

Created on 22 October 2024, about 2 months ago

Overview

Currently, the /xb-components HTTP API response returns a list of XB Components (represented by Component config entities).

Over time, the list of key-value pairs in there has grown organically. They have been documented in /openapi.yml.

But … πŸ“Œ Add support for Blocks as Components Active is changing that: soon there will be multiple types of XB Components.

Proposed resolution

  1. Prepare /xb-components' controller to not hardcode an assumption on SDCs, hence paving the path for πŸ“Œ Add support for Blocks as Components Active . Specifically: metadata, field_data and dynamic_prop_source_candidates may not exist for other component types. (They may need renaming but that is out of scope.
  2. Update the XB UI's client side accordingly

User interface changes

πŸ“Œ Task
Status

Active

Version

0.0

Component

Page builder

Created by

πŸ‡§πŸ‡ͺBelgium wim leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024