doubt about state

[P90Costa]

When i get the state from the Puck API, it only returns the data and UI, but I wanted the items to do

const contentIds = useAppStore(
useShallow((s) =>
zoneCompound ? s.state.indexes.zones[zoneCompound]?.contentIds ?? [] : [] ) );

I'm creating an alternative outline with drag and drop. and I don't know if component is slot and who his children are

[FedericoBonel]

Hey @P90Costa! Just to confirm, you want to iterate through the tree, right? If so, you might be able to achieve that with the walkTree utility function.

[P90Costa]

when I create a slot in a component with one or more. Exemple i have two slot, leftCollum and rightCollum, how do I know id = "Grid-464b9d40-26a2-4424-94d6-d634b8f2bf91 " have children and others do not

I m sorry about the image :)

[FedericoBonel]

Hey @P90Costa! Sorry for the delayed reponse, you want to check if you have children inside a slot? Where would you like to check for this?

[P90Costa]

I wanr create my costum outline

[FedericoBonel]

Hey @P90Costa!

The data object returns the entire data tree, which you would use to build the outline with the walkData utility I linked earlier. The process would look like this:

1. Get the data.
2. Iterate through it using the walkTree utility.
3. As you iterate, build the outline from the bottom up. The walkTree utility provides the parentId and the name of the current slot, which allows you to determine whether a component has a slot and who its children are.

Another option is to iterate through the data yourself (using DFS):

1. Get the data.
2. Go through your config.components and map which component types have fields defined with type === "slot", along with the names of those fields.
3. Iterate through the content property.
4. For each node:
   1. Get its component type.
   2. Check whether its type has a slot using the map you created for all component types.
   3. If it does, continue the loop for all of its children.
   4. Render an element for the current node in the tree.
   5. Continue with the next node.

Does that make sense?