@ryanbrush: Is there any way to reference elements of the rule itself, within the rule?

@ryanbrush: for instance, it would be cool if I could bind $?name $?docstring or $?lhs

So I could push forward some additional metadata about the rule which inserted a fact, for instance

@devn It's not in the public API, but the clara.rules.engine/rule-context dynamic var is populated when a rule is firing. So you could do something like (get-in clara.rules.engine/rule-context [:node :production]) , which would have :name and :doc properties.

@ryanbrush: ah perfect

@devn It would be simple to add a (current-rule) function that just returns that to the public namespace as well. I can see how it would be useful.

Do defrules and queries allow meta on them when defining them?

like (defrule ^{:cool true} "foo" ... => ...)

err forgot the name there

but you catch my drift

It doesn't use meta (but that would be add-able). This might be a good case for rule properties. You could do (defrule my-rule {:cool true} "doc here" ... => ...) This is how rule salience is set but you can put arbitrary properties there.

See the salience example for the structure: http://www.clara-rules.org/docs/conflictsalience/

ah, just discovered that while reading the source

please excuse my laziness

No worries.

I ran into a situation with salience and accumulators. I don't have a simple repro as it was a month ago or so now

it was a custom accumulator, so probably a good chance it was my fault

but i was curious if you were generally aware of any problem that might exist when accumulating and using salience

@devn I'm not aware of any issues with salience and accumulators, although we've used both pretty extensively. If you are able to reproduce something we'd definitely want to track it down.