consider flattening __ASYNC_PROPS__ for client hydration about async-props HOT 1 CLOSED

without jumping to the complexity of something like redux before it is necessary.

That's the idea :)

I've started with a setup that is a bit different than what is suggested here.

If you want to break out of the abstraction then its on you to deal with the hoop jumping. The internal data structure is not public API. I'm not sure why you would want to use async props for data loading in the client but not the server.

With the goal of trying to keep complexity low, I've started with a setup that is a bit different than what is suggested here.

I'm wondering what about async props is making you feel like you need to break away from it to decrease complexity.

Happy to talk about your use-case, but the internal state of AsyncProps, and the shape of the data it stores, won't ever be public API.

from async-props.