Closed (fixed)
Project:
Experience Builder
Version:
0.x-dev
Component:
Page builder
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
15 Jan 2025 at 17:15 UTC
Updated:
4 Mar 2025 at 06:04 UTC
Jump to comment: Most recent, Most recent file

Comments
Comment #2
balintbrewsComment #3
balintbrewsComment #4
wim leers… but per that issue, it'll be exactly like SDC props. So that means … that this can get started ahead of that issue being done? :)
Comment #5
wim leersThis issue summary does not explicitly state which JSON schema types should be available to pick from while defining props for code components.
Are you aware that
type: arrayandtype: objectare both impossible to support at this time? Which means that this issue would be restricted to "primitive/scalar" JSON schema types.Citing the relevant bit of config schema that landed in #3499927: Config entity for storing code components:
Comment #6
balintbrewsYes, I was aware. We'll, of course, need to conform to whatever #3499927: Config entity for storing code components can support in terms of schema and whatever the current capabilities are when it comes to rendering a component props form (which will happen in #3498889: ComponentSource plugin for code components).
Comment #7
effulgentsia commentedComment #8
balintbrewsComment #11
balintbrewsCrediting @callumharrod for helping with the design.
Comment #13
balintbrewsWe made an attempt to add auto-save in this MR, but it didn't work out as easily as I hoped. Let's land that in a new issue.
Comment #15
balintbrewsComment #17
balintbrews@jessebaker, I deeply appreciate your swift review and thorough feedback. Thank you for helping to land this. 🚢
Comment #18
effulgentsia commentedComment #20
lauriiiComment #21
wim leersLooks AMAZING! 🤩👏
Looking forward to being able to save it in #3506424: Loading and auto-saving an edited code component 😄
Comment #22
wim leersSignaling this still needs a screencast/GIF.
Comment #23
balintbrewsComment #24
balintbrews