Kevin C

That sounds about right -- if the list has infinite sections, they couldn't possibly flatten them all. Yay, functional programming! It certainly needs some testing, but I like your solution....

Awesome! I left comments there addressing the above.

I made a few minor style tweaks. I think I might be passing in the wrong data format because I get `TypeError: Expected [K, V] tuple` at `utils.flattenMap` at `reduce`...

It's all good, I know how life can be. Tests would be great, and will probably resolve my issue! Either by helping me understand the data format or by catching...

Hmm, it still doesn't seem to work with the example app using the code diff I pasted above. The list is simply blank (though no errors anymore). It also gets...

In an earlier version of RN + yarn you could simply `npm install file:..` which took about 5 seconds and it would live update. This no longer works unfortunately. It...

I know there are other automated solutions; if you're familiar with one feel free to recommend it. I've never needed something like that until now since the npm trick used...

The items display now, but it shows `123` as the section header instead of `sec1` as expected. There are also still 4 "Loading" rows. The code in `GenericListExample` might need...

My intuition is that we should use the same data format conventions as the original ListView, but the function arguments should be formatted like `VirtualizedList` for consistency. **Eventually** I'd love...

@thomasthiebaud did you ever find the cause of the warnings? I'm getting the same thing: ``` UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): BadRequestError: The value of "state" is invalid,...