Code component status is not reflected in the code editor

the updated status is not reflected in the code editor when the component's code is edited, which is supposed to lock props and slots

This 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.

#4 🐛 Code component status is not reflected in the code editor Needs work : That is unrelated to this issue. It was done in ✨ Editing components sourced as code components Active , and 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.

Didn't mean to block this issue on #4, I just left it as a note that we need a follow-up issue to discuss how we could improve this experience.

wim leers → credited jessebaker → .

Agreed with #5. That requires us knowing whether there's any instances of the code component, as described by @tedbow at #3500043-3: Publishing code components → .

@lauriii requested an explicit follow-up, which is totally reasonable. That's something that should've been created in #3500043 already, per #8.

Created the requested follow-up: 🌱 Plan to allow editing props and slots for exposed code components Active .