Rules builder - set logical operator with specific fluent methods

[luispfgarces]

When adding composed nodes to rules, the fluent interface available on rules builder is:

(...)
return b.AsComposed()
    .WithLogicalOperator(LogicalOperators.Or)
    .AddCondition(cb =>
(...)

Which creates a experience issue given LogicalsOperators has literals And, Or and Eval. The literal Eval is not valid for composed nodes, but the following configuration is possible:

(...)
return b.AsComposed()
    .WithLogicalOperator(LogicalOperators.Eval)
    .AddCondition(cb =>
(...)

So in order to avoid framework consumers from using the framework this way, the proposal is to deprecate method WithLogicalOperator(LogicalOperators logicalOperator) and expose 2 new specific fluent methods on builder:

• WithAndLogicalOperator()
• WithOrLogicalOperator()

Deprecated method would be removed on next major release.

[Daniel-C-Dias]

Will lose scope after the development of https://github.com/Farfetch/rules-framework/issues/138

[luispfgarces]

Resolved by #138.