jods

For those wondering, @istrau2's approach is to use a decorator to add `getObserver` to the getter of properties that are `Promise`. They can then be bound to like a regular...

Yeah some of those remarks occured to me as well. I'm not 100% decided if Promises should get a first-class citizen treatment or they are just a built-in binding behaviour....

First off I'd like to say that I think this is not an easy design issue and I'm kind of thinking aloud here. That's why you may sometimes have the...

> I definitely like the "binding to the promise state" behavior parameters, but the basic promise object doesn't actually expose these, does it? A basic promise is an object that...

> I'd also like to put to rest talk about "just do the right thing". We are not going to add logic to search for Promise and Observable instances throughout...

@niieani It seems very strange to me that you display `promise2` based on `promise1` resolution?! This seems unlikely and could be accomplished by using `if.bind="promise1 & async-resolved"`; or a value...

@niieani ``` ts @asyncBinding getPromiseValue(updateBinding, disposeBinding) { this.then((result) => { updateBinding(result); disposeBinding(); }); return "placeholder value"; } ``` Not so fast :smile: I said it's not flexible and it is...

> I just realized the "binding methods" could have a syntax definition similar to Aurelia's binding behaviours or value converters. No need for decorators or the `::` syntax. Indeed `::`...

> How would it be different to what Aurelia currently does when you have binding behaviours or value converters? They are not in the middle of the expression. Aurelia finds...

I've been thinking about this some more. I thought about Rx rather than Promise just to get another point of view for a moment. I ended up with two different...