Skip to content
This repository has been archived by the owner on Dec 19, 2017. It is now read-only.

JsProxy fields should be enumerable? #618

Open
jakemac53 opened this issue Oct 7, 2015 · 1 comment
Open

JsProxy fields should be enumerable? #618

jakemac53 opened this issue Oct 7, 2015 · 1 comment
Labels
Milestone

Comments

@jakemac53
Copy link
Contributor

Today they are not, but they probably should be (or at least I don't see a reason why not).

One potential issue, on the JS side they may try to JSON encode these objects, and then JSON decode them back. The object they get back won't be tied to a dart object or type any more, so its going to act just like a normal js object and get converted to a dart map. Today they will just get an empty object since the fields aren't enumerable, so at least it kind of throws up a red flag that something is not working as expected.

@vimalraj-a
Copy link

This issue been created since 50 days before..... Still no one assigned to this?

Any idea when this can be resolved. Seems I cannot use Firebase-Collection polymer element.

Please fix this issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Development

No branches or pull requests

2 participants