PanelGroup can't provide a meaningful layout for Panels during the initial render because it doesn't yet know about their constraints. Panels register constraints with the parent PanelGroup on mount, which schedules an update so that PanelGroup can re-render them.
If a parent component uses Panel or PanelGroup imperative APIs on mount (before the scheduled update) the values returned won't be meaningful, and in some cases can even error.
I think the way to work around this is to move layout calculation from an effect to the registerPanel method and to eagerly calculate layouts once all panels have registered.
Related to #211
PanelGroupcan't provide a meaningful layout forPanels during the initial render because it doesn't yet know about their constraints.Panels register constraints with the parentPanelGroupon mount, which schedules an update so thatPanelGroupcan re-render them.If a parent component uses Panel or
PanelGroupimperative APIs on mount (before the scheduled update) the values returned won't be meaningful, and in some cases can even error.I think the way to work around this is to move layout calculation from an effect to the
registerPanelmethod and to eagerly calculate layouts once all panels have registered.