Immutable.KeyedIterable as children

I’m aware of the Iterable support for children, but is there any timetable for supporting KeyedIterable from Immutable.js, specifically for automatically providing keys to children?

Sample use case:

var myItems = Immutable.Map({ // extends KeyedIterable
  one: 111,
  two: 222
});
var renderedItems = (
  <ul>{myItems.map(item => (
    <li>{item}</li>
  ))}</ul>
);

That is, the first item would end up the equivalent of <li key="one">111</li>.

If such support isn’t on the roadmap, can I somehow avoid having to use React.cloneElement() (which will have performance implications) if I write a helper function that does this?

[markuslerner]

Same here. Any news on why React iterates both valueSeq() and entrySeq() twice? This still happens to me with React 15.4.2.

Using Immutable.Map.map() directly and ignoring the error “Using Maps as children is not yet fully supported” works fine though, which is weird.

[nikolas6]

This happens to me too. React iterates entrySeq() twice. This is the first thread I found so far that mentioned this issue.

Just wondering, do you guys keep using entrySeq() that iterates twice? or using .toArray() first or .map() directly to iterate once?