[0.8] x-repeat should support iterating object-valued items

[kevinpschaaf]

Currently only arrays are supported. Object (and possibly Map) values should also be made iterable.

This was requested in the Polymer 0.5 codebase per googlearchive/polymer-expressions#11.

[arodic]

Yes, please, please please.

[lgersman]

👍

[chuckh]

+1

[RB14]

I'll add to that and suggest adding support for any iterable object (including generators and other user-defined iterables). I think I requested it in 0.5 few months ago.

[ganadev]

+1

[ternite]

+1

[mcarey1590]

+1

[knowlecules]

+1

[alecbz]

+1

[harsimranmaan]

+1

[Jamtis]

+1

[jialic]

+1

[kuma-guy]

+1

[kingflurkel]

+1

[laurajmaddox]

+1

[b0c1]

+1

[zmoshansky]

Please use the "Subscribe" feature under notifications in the right pane instead of +1'ing this into oblivion; Then everyone avoids getting spammed with useless notification emails.

[Jamtis]

In order to iterate over objects or iterables the 'items' property of the 'dom-repeat' template must differ from Array.
Can be found here.

After thinking about this a little bit I guess the best thing is to set the type to Object to support all Iterable objects.

[Jamtis]

When iterating over key-value iterable should index represent the key or should there be a separate key property?

[jarede]

+1

[Jamtis]

A possible solution could be to internally convert all Iterable (Object, Array, Set, Map, Generator) to a Map.

I don't know how performant this solution is...

Does someone have a better way to do it?

Additionally:

If we want to support Set/Map (generally) Polymer needs a way to listen to changes made to them.
Polymer can't even listen to Array changes natively, element.push is required.
So Polymer has to implement Set/Map method also... as I stated in #2074.

[fernandojsg]

Any updates on this? :\ one of the biggest downside I've found on polymer right now

[bvhme]

The new Firebase element does no longer support an array like collection AFAIK, this makes an iterable template for objects a lot more relevant again I hope.

[klarkc]

A big blocking here, of course, because of Firebase element changes.

[cleaverpj]

+1

[Arual90]

+1

[monkybrain]

+1

[krozycki]

+1

[sreekrishna]

+1

[derhuebiii]

+1

[diegocerdan]

Does Polymer 2.0 help with this issue? Every time I start side-projects using Polymer I step into this problem.

[Pablo-Aldana]

+1

[dwelby101]

+1 This would be a really neat feature to have

[NicolasRannou]

+1

[baocang]

+1

[derhuebiii]

Polymer 2.0 doesn't seem to have this functionality either? At least I cannot find it in the specs?
Are there any plans to implement this? Was hoping so much for Polymer 2.0 ...
https://www.polymer-project.org/2.0/docs/devguide/templates

[togonow]

+1

[Geoffrey-Pliez]

+1

[jogibear9988]

same as #800 maybe close one

[LarsDenBakker]

+1 seems like such a basic functionality

[derhuebiii]

Are there any plans for this to come?

[CollectionAgency]

When will there be a fix for this nonsense?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed after being marked stale. If you're still facing this problem with the above solution, please comment and we'll reopen!