Changing prop name from UI doesn’t change prop name at backend

Created on 23 July 2025, 3 days ago

Overview

Steps to Reproduce

  • Create Code component , add text prop mark it as required and name it as "Test" and link it to UI
  • Add to Component and the to page
  • Publish the changes
  • Remove component from page and then from components list
  • Edit component
  • Change Prop Name to. "Test Edit"
  • Add to components

Proposed resolution

User interface changes

πŸ› Bug report
Status

Active

Version

0.0

Component

… to be triaged

Created by

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

Comments & Activities

  • Issue created by @neha_bawankar
  • πŸ‡§πŸ‡ͺBelgium wim leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί

    Please provide the corresponding Component config entity at each stage. Specifically, any change to the code component that is *saved* (not auto-saved, but actually saved) SHOULD result in an update to the code component's Component config entity.

    (That would be experience_builder.component.js.[machine name of code component].)

    Export it either using drush cget or at /admin/config/development/configuration/single/export

    Remove component from page and then from components list

    This is very hard to interpret. I think the first time "component" really means "component instance", and the second time you're removing the code component from

    Please always use the term "component instance" when referring to an instantiation of any component (no matter whether it's an SDC, code component or block plugin).
    "component" refers to the generic concept that can be instantiated, represented inside XB itself by the Component config entity β€” which is how XB knows about a component coming from some source (SDC is a source, code components are a source, block plugins are a source).

Production build 0.71.5 2024