- Issue created by @balintbrews
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
Crediting @tedbow for #3500043-3: Publishing code components → .
Code components, once they're added to components, i.e. become exposed, lock props and slots. This was implemented in ✨ Editing components sourced as code components Active .
On a related issue, 🐛 Code component status is not reflected in the code editor Needs work , @lauriii raised the following:
the updated status is not reflected in the code editor when the component's code is edited, which is supposed to lock props and slotsThis seems like a pretty drastic consequence. I think we need follow-up issue to find a better way for managing this because it's fairly normal that especially during the initial development of a site that props might change.
Comment by @balintbrews:
[...] it was an easy consensus within the team that we need to ensure that once a component is exposed, which means it can be used for content, we need to ensure data integrity. Props can be updated by moving the component back to internal, where the prerequisite is that it's not used on the page. Maybe we can forego locking props and slots when that prerequisite is met. Happy to discuss in a follow-up.
Comment by @Wim Leers:
Agreed with [comment by @balintbrews]. That requires us knowing whether there's any instances of the code component, as described by @tedbow at #3500043-3: Publishing code components →
Let's discuss and plan how we could improve this.
TBD
Active
0.0
Page builder
Crediting @tedbow for #3500043-3: Publishing code components → .