Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

removing binding and condition methods as they cause conflicts, use "…

…b" and "c" instead
  • Loading branch information...
commit b6179c2a939688413e1502b431038aab3846f94f 1 parent 0b09875
Matt Smith authored
Showing with 1 addition and 9 deletions.
  1. +1 −9 lib/rule_helper.rb
View
10 lib/rule_helper.rb
@@ -35,19 +35,11 @@ def method
def b(variable_name)
Ruleby::Ferrari::BindingBuilder.new(variable_name)
end
-
- def binding(variable_name)
- b variable_name
- end
-
+
def c(&block)
return lambda(&block)
end
- def condition(&block)
- return lambda(&block)
- end
-
def OR(*args)
Ruleby::Ferrari::OrBuilder.new args
end

1 comment on commit b6179c2

@skalnik

Why specifically were these removed? I'm looking into using Ruleby for a project I'm working on, and this is discourages me from using it a bit. Ruby puts emphasis on readable code, but a rule definition with only b and c can look really confusing and requires someone to look up documentation, or rely on code comments.

Is there a possibility of adding these back? Or perhaps if there's an issue with the method names, naming them something else?

Please sign in to comment.
Something went wrong with that request. Please try again.