You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#60 made the request for a new `object data type for more complex, nested data shapes to be managed by Puck fields.
This was proposed in PR #62, but it was decided that the array interface might not be appropriate for this, and that we are conflating 1) UI concerns and 2) data model concerns.
Consequently, we closed #60/#62 and opened #64 to handle 1) the UI rendering by introducing a React-ish renderFields API.
Proposal
Option 1 - Nested paths
#64 handles the UI-layer for rendering complex objects. Additionally, we could allow for reaching into nested objects via the field API
#60 made the request for a new `object data type for more complex, nested data shapes to be managed by Puck fields.
This was proposed in PR #62, but it was decided that the
array
interface might not be appropriate for this, and that we are conflating 1) UI concerns and 2) data model concerns.Consequently, we closed #60/#62 and opened #64 to handle 1) the UI rendering by introducing a React-ish
renderFields
API.Proposal
Option 1 - Nested paths
#64 handles the UI-layer for rendering complex objects. Additionally, we could allow for reaching into nested objects via the field API
Option 2 - object field type
The original proposal from #62, we could implement an
object
field type that reuses the array API and UI.Option 3 - combo
We could also offer both APIs and allow the user to determine what is best for their use-case.
Considerations
The text was updated successfully, but these errors were encountered: