Add Some More Syntactic Sugar to the DSL about rulebook HOT 6 CLOSED

Having an option where NEXT and BREAK don't have to be returned also allows for other (non procedural) rules chaining options. Although I think RuleBook will always have sequential chaining at its core, the focus has to be on an intuitive and flexible interface. That was the whole reason for RuleBook in the first place -> something that could be picked up and used effectively in an hour or two (at most).

from rulebook.

I also think that there should probably be an easier way to extract facts in the DSL. Using Fact objects is nice since it guarantees a reference - Facts hold references, and even do cool stuff like keep up with changes to immutable objects (e.g. Strings). But you shouldn't always have to know they are there or work directly with Fact objects or the FactMap object in the DSL. Modifying the given() is a great first step. But the next step is making Facts transparent in their usage in Rules.
What about something like the following?

StandardRule.create().given("hello", "Hello").given("world", "World").when(f -> true).using("hello").then(System.out::println).using("world").then(System.out::println); //this would print "HelloWorld"

or this would also work

StandardRule.create().given("hello", "Hello").given("world", "World").using("hello").then(System.out::println).using("hello").then(System.out::println); //this would print "HelloWorld"

or in a RuleBook (where Facts are automagically supplied to Rules)

StandardRule.create().using("hello").then(System.out::println).using("world").then(System.out::println); //this would print "HelloWorld"

from rulebook.

It looks like doing the above stuff will break the existing DSL, which I am not a huge fan of doing. But I do think it will yield a nicer to work with DSL and a more rich language.
This would not affect POJO rules, however.

from rulebook.

The DSL is mostly intact. All the old stuff will still work with one exception: then methods can't return anything. In lieu of having to return RuleState from a then method, the new stop method is introduced. By chaining the stop verb, it signals the rule to break the rule chain after the then action is executed, which also means the when condition must be true for the rule chain to be broken.

from rulebook.

Branch Issue36_SyntacticSugar contains the completed and working code. All tests are passing.
All that's left now to ensure that coverage is up to snuff given the new changes and JavaDocs are updated appropriately.

from rulebook.

These enhancements have been pushed out to 0.3.5-SNAPSHOT and merged into the develop branch.

from rulebook.