[Flight] Let Errored/Blocked Direct References Turn Nearest Element Lazy #29823

…he end

While JSON.parse doesn't let us inspect the begin/complete phase to push/po we can rely on the REACT_ELEMENT_TYPE marker being a leaf that's in the beginning of the element as the begin an the element itself is the complete phase. This lets us more deeply handle suspense or errors in case there's an Error or Suspense boundary in the current model. The tricky bit is to keep in mind cycles and deep references that might now be broken apart.

It's just a blocked chunk that eagerly calls its listeners.

…ped.

We feel comfortable turning any Element into Lazy since it serializes as Node. So if any error happens inside of the deserialization such as if a direct reference errored or a client reference failed to load we can scope it to that element. That way if any Error boundaries were on the stack inside the same model, they can handle the error. This also gives us better debug info for things like serialization errors because they now can get a stack trace pointing to the exact JSX.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Flight] Let Errored/Blocked Direct References Turn Nearest Element Lazy #29823

[Flight] Let Errored/Blocked Direct References Turn Nearest Element Lazy #29823

Commits on Jun 11, 2024