Going live!

Updated dependencies. No further changes.

0.2.0

Chaining rules with AND/OR

0.1.0

• Make closures work both sync or async. Closure invokers (Rule, RuleFlow, ClosureReducer) won't create a Promise and execute on the then if the called closure returned a sync result. Engine will always return promises, so high level API hasn't change.
• Totally remove co dependency
• Fix unit tests! There were a lot of false positives on tests due the removal of co-mocha from dependencies.

Remove dependency to co

Reimplemented through native Promises

Remove dependency to async-class-co

It was replaced by plain old co library.

Fix performance issue with Context.bindParameters

This internal issue might cause huge delays on fact processing. By changing the clone algorithm from
JSON.parse/stringify to Object.assign we achieved a 5x performance boost.

Add matchOnce option for RuleFlows

v0.0.6

add matchOnce option for rule flows

Add support to register closures classes

Added support for #6 and #7

Disabled required parameters validation at bind time (since it was broken)

Introduce template method for object closures

Now closures implemented thorugh a class must define a do method instead of a process method (although, overwriting process is still an option`.

do method accepts non promise return values.

0.0.3

Major changes. Closure syntax consolidated. Reduced to minimum interfaces.