Check that references don't conflict in letigre
Reported by Matt Smith | June 23rd, 2008 @ 09:11 AM | in 0.5
In the letigre syntax, it is possible to have bindings conflict with method names. For example:
rule 'New Ticket', {:priority => 10}, # :duration => 10},
'exists? Customer as :customer',
'exists? Ticket as :ticket where #customer == #:customer' do |e,vars|
puts 'New : ' + vars[:ticket].to_s
end
Would create a code block:
lambda { |customer,customer| customer == customer }
We also need to make sure the the binding converted to string does not conflict with any other variables.
Comments and changes to this ticket
-
jpkutner (at gmail) December 29th, 2008 @ 08:41 AM
- Tag set to “dsl, dsl-letigre”
- State changed from “new” to “invalid”
Le Tigre has been deprecated
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
the Rule Engine for Ruby
jpkutner (at gmail)
Matt Smith