It's not uncommon for 1) an updateComponents message to describe a component that reference other components as its children and 2) the client hasn't heard a thing about those children yet (that often arrives in a follow-up UpdateComponents message that comes right after the first).
In this scenario, wouldn't the lookup return nil and every caller just drops its job of rendering this subtree because resolveChildList skips nil children.
In this scenario, our prior art implements progressive rendering, putting placeholders in place of children that have yet to arrive. I don't remember off the top of my head how much better this tends to look compared to the more classical approach of just having components pop in as they arrive, so your mileage may vary.
Originally posted by @andrewkolos in #2052
Once the Basic Catalog and Sample App are up and running, finalize the behavior of declared but missing (or incomplete) render nodes. Perhaps with a placeholder view or perhaps pop-in.
Originally posted by @andrewkolos in #2052
Once the Basic Catalog and Sample App are up and running, finalize the behavior of declared but missing (or incomplete) render nodes. Perhaps with a placeholder view or perhaps pop-in.