Consider whether to store Component entities outside of config when in demo_mode

Created on 9 January 2025, 11 days ago

Overview

I don't know if the following is sensible or not, it's just a half-baked idea...

In demo_mode, I don't think we're creating any config entities other than Component. And the Component config entities aren't even really configurable yet (maybe they will be in the future, but not yet): they're auto-generated from SDC info. Which leads me to wonder, what if we implemented Component::load(), Component::save(), and friends to when in demo_mode to just read from and write to a KV store and bypass all entity hooks? That way, if in the future we wanted to implement a destructive update path (just a "delete all XB stuff and reinstall defaults" update function), we'd avoid the problems described in #3497543-7: Milestone 0.2.0: the one for Drupal CMS 1.0 β†’ .

Proposed resolution

Think about it. Maybe create a POC MR. If it seems too big an effort or potentially too problematic, it's okay to not do it.

User interface changes

✨ Feature request
Status

Active

Version

0.0

Component

Config management

Created by

πŸ‡ΊπŸ‡ΈUnited States effulgentsia

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

Comments & Activities

Production build 0.71.5 2024