If we're going to update the height, I think we have no choice put to put the value in render state

I just tried makinga test component to see what would happen if we don't put height changes in state, and it feels like it's too easy to accidentally wipe the adjustments away

I think I'd do something like this:

const[contentHeight,setContentHeight]=useState<string>()constcontentRef=useRef<HTMLDivElement>(null);useLayoutEffect(()=>{// It's been a while since I've had to do this, but dispatching a state update from the// resize callback might actually be too slow, and you might get a UI flicker still. You// might need to set up the resize callback to dispatch state updates, but then also// do a one-time direct mutation when the effect first mounts},[])css={{height:contentHeight||"100%"}}

I think we have an edge case here that could break the effect logic:

1. Component mounts with no build
2. We set up the ref and effect to run after the first render
3. The first render completes, but because there's no build, we return out a loader and don't attach the ref to anything
4. The layout effect runs and whiffs
5. We re-render at some point with a build, but because the layout effect dependency array is empty, nothing in it re-runs
6. The only way to get the size mutations to apply at this point is if the browser resizes, but if the user never resizes anything, we're stuck with the same issue as before

Wondering if might be best to make a new component boundary and move this state there. That way, the state only mounts when we're guaranteed to have a build

Tiny thing, but could we set the type to be based onCSSProperties["height"]>?

lol yes, idk why I used width 🤦