React Concurrent Mode

Re:React Concurrent Mode by erikpukinskis on Thursday October 24, 2019 @08:11PM (#21350474)

Render functions, to my knowledge, can’t return a promise.

(And you don’t throw a promise, you return and reject it)

The issue at hand is fully synchronous render functions that, e.g., go through a giant list of objects and call a bunch of other render functions on each one synchronously.

This change allows that one function to finish, and interaction to continue before all the children render.

[ Parent | on HN ]

Re:React Concurrent Mode by jbaudanza on Thursday October 24, 2019 @08:14PM (#21350492)

The new suspense API works by throwing Promises when the data isn't ready yet.

[ Parent | on HN ]

Re:React Concurrent Mode by erikpukinskis on Sunday October 27, 2019 @12:59PM (#21370900)

I’m not sure what you mean by “throwing promises”...

You mean returning unresolved promises? Or returning rejected promises? Or just throwing an error?

[ Parent | on HN ]

Re:React Concurrent Mode by acemarke on Monday October 28, 2019 @11:39AM (#21377915)

Literally, _throwing_ a Promise.

React will catch promises thrown during rendering, and treat that as a request to "suspend" the component and come back to it later once the promise has resolved.

[ Parent | on HN ]