Polymer: [0.8] x-repeat should support iterating object-valued `items`
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 https://github.com/Polymer/polymer-expressions/issues/11.
kevinpschaaf
All 53 comments
Yes, please, please please.
arodic
on 8 Apr 2015
:+1:
lgersman
on 9 Apr 2015
+1
chuckh
on 9 Apr 2015
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.
RB14
on 9 Apr 2015
+1
ganadev
on 20 Apr 2015
+1
ternite
on 21 Apr 2015
+1
mcarey1590
on 8 May 2015
+1
knowlecules
on 12 May 2015
+1
alecbz
on 4 Jun 2015
+1
harsimranmaan
on 21 Jun 2015
+1
Jamtis
on 10 Jul 2015
+1
jialic
on 6 Aug 2015
+1
kuma-guy
on 28 Aug 2015
+1
kingflurkel
on 4 Sep 2015
+1
laurajmaddox
on 5 Sep 2015
+1
b0c1
on 5 Sep 2015
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.
zmoshansky
on 5 Sep 2015
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
on 29 Sep 2015
When iterating over key-value iterable should index represent the key or should there be a separate key property?
Jamtis
on 30 Sep 2015
+1
jarede
on 2 Oct 2015
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.
Jamtis
on 3 Oct 2015
+1
jmcgdz
on 13 Oct 2015
+1 I would love this.
mercmobily
on 14 Nov 2015
+1
LuisTJap
on 17 Nov 2015
+1
jgautheron
on 20 Nov 2015
status?
MeTaNoV
on 14 Dec 2015
Is anyone from the polymer team actively working on this?
Otherwise I'll take a deeper look into this.
Jamtis
on 15 Dec 2015
BIGGEST +1
chunkzer
on 17 Dec 2015
This line states that the itemsproperty of dom-repeat is an array.
Therefore we need a more general type to cover all iterable objects.
@kevinpschaaf What do you think about an "Iterable" type?
Furthermore Polymer.Collection handles the given array interally @ line 348.
Thus Collection must support all Iterables.
Critical parts are here, this loop must also cover other iterables.
Jamtis
on 22 Dec 2015
+1
alodavide
on 11 Mar 2016
I needed a solution for this so I wrote something. Since I don't know Polymer internals and did not want to work with a modified version anyway, I had to make do with what's there. I transform the Object into an array once and then propagate only the changes up and down. It does not handle key additions/removals and array splices but otherwise it's fully transparent. Maybe some of it is of some use here. Usage:
<my-objarray object="{{object}}" array="{{array}}"><my-objarray>
<template is="dom-repeat" items="{{array}}">[[item.key]]: [[item.value]]</template>
The code is on stackoverflow.
schrotie
on 14 May 2016
Any updates on this? : one of the biggest downside I've found on polymer right now
fernandojsg
on 18 May 2016
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.
bvhme
on 3 Jun 2016
A big blocking here, of course, because of Firebase element changes.
klarkc
on 19 Aug 2016
+1
cleaverpj
on 8 Oct 2016
+1
Arual90
on 26 Oct 2016
+1
monkybrain
on 12 Nov 2016
+1
krozycki
on 14 Dec 2016
+1
sreekrishna
on 29 Dec 2016
+1
derhuebiii
on 2 Jan 2017
Does Polymer 2.0 help with this issue? Every time I start side-projects using Polymer I step into this problem.
diegocerdan
on 23 Feb 2017
+1
Pablo-Aldana
on 5 Mar 2017
+1 This would be a really neat feature to have
dwelby101
on 14 Mar 2017
+1
NicolasRannou
on 3 Apr 2017
+1
baocang
on 5 Apr 2017
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
derhuebiii
on 18 Apr 2017
+1
togonow
on 18 Sep 2017
+1
Geoffrey-Pliez
on 2 Oct 2017
same as #800 maybe close one
jogibear9988
on 19 Nov 2017
+1 seems like such a basic functionality
LarsDenBakker
on 11 Dec 2017
Are there any plans for this to come?
derhuebiii
on 9 Feb 2018
When will there be a fix for this nonsense?
SoufianAkh
on 10 Apr 2018
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[bot] picture](https://avatars.githubusercontent.com/in/1724?v=4&s=40)
stale[bot]
on 13 Mar 2020
Related issues
bmodeprogrammer
路
3Comments
fabysdev
路
3Comments
ghost
路
4Comments
myuseringithub
路
3Comments
mbana
路
3Comments
Most helpful comment
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.