Jeremy

lets see if i am following: 1. Although this is outside the scope of this issue, but in response to your last post: @zewa666 there are a few plugins that...

@zewa666 I do not see a problem with this change as I hardly ever use the `newVal` argument with Aurelia's change handling since the value is already set. I think...

@zewa666 I can work on this since I am familiar with the changes I submitted for the `connectTo` decorator. @Vheissu yes i agree, especially when using the aurelia-router because `activate`...

To be honest, I only did this since I called myself out in #69 to fix this and did not want to keep anyone waiting. However, after I finished and...

I'll start off with a simple approach, very similar to `connectTo`. Below are two rough draft proposals that decorate aurelia-router `activate` and `deactivate`. This is just an example, a better...

@zewa666 I updated my example to be more complete while trying to keep it simple (e.g. I removed the double underscore, which i use for namespacing actions, similar to the...

@zewa666 have you thought about/tried adding a static instance property to the store so we do not have to depend on the container in decorators? Seems it is in `dispatchify`...

No worries. I know how busy life can be and i do not think this feature is super urgent. I am all for companion plugins as that is a good...

@bigopon thanks this looks great and i've implemented the logic in my own decorators. The only issue I have is integrating the decorators with aurelia-router since `activate` gets called before...

I like this idea. Scaffolding helps with boiler plate code exhaustion and is great for speedy development, especially with crud-like apps where you find yourself doing the same thing over...