Charles Solar

Been struggling with async a bit in aurelia and came across this discussion. So outside lifestyle hooks loaded from the router `async` is kind of a mess atm? Seems the...

Defined rules would be internal aggregate.net data - which would mean an internal aggregates.net stream. Perhaps the projection we're planning in #33 can be useful

Should accomplish this via a pipeline behavior Rules can be defined on commands, the behavior would load and evaluate any dynamic rules on a command A user would add/edit/remove rules...

Thinking about this issue - while it was a good idea at the time there is a big issue. Given an endpoint that has 10 different event namespaces and maintains...

@galenp breaking up the projection into many pieces is pretty easy to do - but while I was working on it I thought about what would happen if - say...

I was thinking it would be better to just update the projection when starting - and leave it to the user to increment their endpoint's version if they want to...

After a chat - the way I was thinking about splitting was wrong. We'd not be splitting on the event's `Versioned` namespace - we'd be splitting based on the `Handler`...

Upon startup the endpoint would map out which events are handled by which handlers and create a single projection which links events to one of multiple handlers like so ```...

Not immediately clear - but what I meant was to support upgrading/downgrading events into different versions.

Just ran into this issue - only need to know if its building on VSTS so now I'm doing `var isVSTS = buildSystem.TFBuild.IsRunningOnVSTS || buildSystem.TFBuild.IsRunningOnTFS;` instead of just `IsRunningOnVSTS `