Bryan Smith

We should make it easier to customize this behavior.

It happens because events are raised using the original instruction, but I agree it's not right. We should raise events using the instruction that actually created that result.

Thanks for the reminder about 'cancelled'. I'll make sure we're using the American English inflection consistently.

No, I need to make an adjustment to the instruction attached to the event. On Mon, Oct 26, 2015 at 8:03 AM Rob Eisenberg [email protected] wrote: > @bryanrsmith https://github.com/bryanrsmith Can...

Cool! I'll give it some thought and try to take a closer look soon. I think it'd be good to try to keep as much of this out of the...

Unfortunately not. I had just started to look at implementing optional route parameters, but haven't written any code yet. There has been a steady stream of fairly important router issues...

I think what we should do for this is pass the hash as a separate property to the route handler so it can be exposed to activated modules as needed....

That sounds reasonable to me. It might be nice to get feedback from someone who wants this feature, though. The simplest thing to do (in terms of implementation on our...

@WouterOuwens Are you able to provide a plunker or link to a repo that demonstrates the problem?

Sorry, but I don't know of any plans to work on this before 1.0. I really want it too, but I haven't had much time to spare lately. If anyone...