Kenneth Truyers

Thanks for the quick response, this is a good workaround However, I don't think this is really obvious behavior. It doesn't work that way with normal bindings either. In the...

Another thing that is different from the normal observables is that whenever the change-handler is triggered, the property itself hasn't been updated yet, whereas with a normal observable when you...

OK, that sounds reasonable, I will have a look at the documentation to see if I can provide an update. In terms of changing the API, maybe it's an idea...

Yeah, that could be a potential solution. I think my main gripe with this behavior is that strays from the way Aurelia normally works. From my point of view, the...

What I mean by 2 is for example this: ``` @autoinject() @connectTo({ selector: { list: store => store.state.pipe(pluck('list')) } }) export class App { store; list : string[] = [];...

Yeah, completely agree, this is really a separate issue. I will create a separate ticket for it. I also agree that it's a breaking change, so it would either need...

Ticket is here: https://github.com/aurelia/store/issues/69

Hm, thinking about it now, I think this change is a bit of a hack on top of it and I think there's a cleaner way to do this. With...

Not really, the root state object may have changed, but the items inside the state will still be the same: ``` State 1 => Object 1 List 1 ``` After...

@zewa666 I had a go at creating a decorator for this, but unfortunately got stuck as well. You can decorate the property and rewrite the getter/setter to it pulls from...