Data binding with JavaScript no longer available in 1.0

[arodic]

In 0.5 there was a handy built-in function this.bindProperty() as well as this.bind() It appears that equivalent functions no longer exist in 1.0. Perhaps this functionality is provided in undocumented Polymer.Bind but without documentation it is hard to tell.

[zerodevx]

I think imperative data-binding is not supported in 1.0 per #1778

[arodic]

we don't currently support this

According to @kevinpschaaf this is "currently" not supported. Perhaps it will be supported in the future?

[zerodevx]

Not sure... But given that data is bounded on registration, I'm experimenting with a (bit hackish) way to data bind imperatively by defining the prototype chain before registration on the fly. Will post results.

On 9 June 2015 15:53:42 GMT+08:00, AKI RODIC notifications@github.com wrote:

we don't currently support this

According to @kevinpschaaf this is "currently" not supported. Perhaps
it will be supported in the future?

---

Reply to this email directly or view it on GitHub:
#1796 (comment)

Sent from my Android device with K-9 Mail. Please excuse my brevity.

[JasonFitz]

Has there been any work on this? Our app hinges on the ability to bind properties to elements created dynamically.

[polpo]

We also use this heavily and would like to know if any work or decisions have been made on this.

[bedeoverend]

Would also love to see this implemented +1

[RobinLinus]

Would also love to see this implemented +1

[saurshaz]

+1
repeating @polpo "We also use this heavily and would like to know if any work or decisions have been made on this."

[zerodevx]

I believe this feature is in the Polymer owners' radar and inside the dev timeline. For certain instances, a (somewhat hackish) workaround that I used to employ was this: #2131 (comment).

Later, I just made some workflow (and mindset) changes that for most times replaced the need for late binding completely. I'll suggest that, or waiting for an official (and true) late-binding API to be released.

[warpech]

I also have a problem with this: I have two Polymer elements which ignore that they are bound to the same object: https://jsfiddle.net/warpech/g4xoqaff/3/

I know that this can be worked around by wrapping them in a single Polymer element, but can't have that workaround. I would like to use a JS API to bind them together.

[devinivy]

@warpech this is possible with a little extra glue– you need to keep track of which components share that object then notifyPath() on each of them when one of them changes it. See the approach in yarn-state-behavior. And perhaps a better/simpler option in this case is to create a third element to house the shared object. This third element could be included in all elements that need to bind to the object.

Also related to this discussion are the existing linkPaths() and unlinkPaths() methods:

polymer/src/standard/notify-path.html

Lines 333 to 365 in acdfc1e

	/**
	* Aliases one data path as another, such that path notifications from one
	* are routed to the other.
	*
	* @method linkPaths
	* @param {string} to Target path to link.
	* @param {string} from Source path to link.
	*/
	linkPaths: function(to, from) {
	this._boundPaths = this._boundPaths || {};
	if (from) {
	this._boundPaths[to] = from;
	// this.set(to, this._get(from));
	} else {
	this.unlinkPaths(to);
	// this.set(to, from);
	}
	},
	/**
	* Removes a data path alias previously established with `linkPaths`.
	*
	* Note, the path to unlink should be the target (`to`) used when
	* linking the paths.
	*
	* @method unlinkPaths
	* @param {string} path Target path to unlink.
	*/
	unlinkPaths: function(path) {
	if (this._boundPaths) {
	delete this._boundPaths[path];
	}
	},

[kaste]

Can you take a look at #3456 (and its related PR #3460) and perhaps comment if that would fix your issue.

[TimvdLippe]

Closing per #3460 (comment) This API shipped in Polymer 2.

[dman777]

👎 What about Polymer 1.*? It is still being supported.