Can you elaborate the design of "Adapter"?

[unixzii]

As far as I learn from the sample, the adapter is an abstract that provides a subtree of the full state for a specific item (which is controlled by a so-called "Component") in list views. Is my understanding correct?

Why can't we just extract the data of one item and pass it to the view, since we can put the logic (reducers & effects) into the containing component? Is that kind of consideration for Divide and Conquer?

[zjuwjf]

Adapter is a better "Component" in ListView.

A ListView could be built by a main adapter which combines many small adapters.
It's similar with a flat-map operator.

1. It solves the big cell issue .
2. It provides two more events, appear & disappear .
3. Adapter's effect part has the same lifecycle as the ListView, whether the view part is visible or not in the ListView.

The example only demonstrated how to use an adapter but didn't show the advantages.

[unixzii]

Now I think I got the point, and the flat-map fashion transformation is also an important thing, cool!

But there are still many concepts (like connector, dependent) that need time understanding, it would be better if there would be some detailed documentation in the future.

Thanks!