Polymer throws warning "Unable to parse JSON" about angular-custom-elements

[robdodson]

Unfortunately I haven't been able to figure out how to modify the template before it hits the page. This means we likely need to use a custom syntax for doing Angular -> Polymer bindings :(

[kasperstorgaard]

We have tested out multiple approaches for fixing this, but have been unable to find a way to change this before polymer kicks in.
If you defer the loading of polymer this only fixes it on first load, not when you load the next page.

My best solution so far has been to use ng-attr-*, where angular will set the attribute itself, and the collision is solved unless you also use ngAttr*as a prop in your element 😛
I then use my own directive similar to this, but with double binding support for ng-attr.
It's not perfect, but you don't need to do
if (/\{\{.+\}\}/.test(val)) { return; }
or similar in your computed's which is way worse.
(^for a String property. for Object/Array you need to test for null after the failed parse)

[robdodson]

yeah I've thought about recommending ng-attr-*. It's kind of a bummer because then you're serializing everything to strings and then parsing them again in Polymer. But it might be the only way around the issue

[kasperstorgaard]

yeah it isn't ideal, but angular 1.x and polymer isn't that great of a match unfortunately.