Thoughts on directDomUpdates

[zeorin]

@piecyk I've been trying out directDomUpdates, and I have the following questions:

1. Why not accept a directDomContainer option instead tacking a ref callback onto the virtualizer instance? That feel more idiomatic React to me.

2. Would it be possible to have applyDirectStyles bail out early if state.container is null? I.e. skip updating the items elements' styles? This is useful if someone wants to bail out of causing some re-renders but want to implement their own direct DOM updates. In my case I have a table with a subgrid layout, and absolute positioning breaks grid for subgrid items, so I must implement my own, because my element transforms needs to be different.

3. The docs for directDomUpdates are published, but AFAICT it's not in a stable release yet… Is that correct?

[piecyk]

Thanks for the feedback, these are good edge cases.

1. On directDomContainer: we used containerRef to keep the API a bit simpler. I’m not opposed to revisiting the shape.

2. On custom DOM updates: agreed that subgrid/table layouts are a case where the built-in absolute positioning is too opinionated for some use cases. For that kind of advanced layout, you can already implement your own version by patching into onChange and controlling the re-rendering behavior in userland.

3. I don’t fully follow the last point. The published docs describe directDomUpdates as writing item positions and container size directly to the DOM, with containerRef required on the inner size container, and this has landed in the released version.