lex-conditioner

Conditional rule engine for LegionIO. Evaluates JSON-based rules against task payloads to determine whether downstream tasks should execute, enabling branching logic in task chains.

gem install lex-conditioner

Or add to your Gemfile:

gem 'lex-conditioner'

Use the conditioner without the full LegionIO framework:

require 'legion/extensions/conditioner/client'

client = Legion::Extensions::Conditioner::Client.new

result = client.evaluate(
  conditions: { all: [
    { fact: 'response.code', operator: 'greater_or_equal', value: 200 },
    { fact: 'response.code', operator: 'less_than', value: 300 }
  ] },
  values: { response: { code: 200, body: 'OK' } }
)

result[:valid]       # => true
result[:explanation] # => { valid: true, group: :all, rules: [...] }

The explanation includes per-rule results with actual values:

result[:explanation][:rules]
# => [
#   { fact: "response.code", operator: "greater_or_equal", value: 200, actual: 200, result: true },
#   { fact: "response.code", operator: "less_than", value: 300, actual: 200, result: true }
# ]

Rules use all/any grouping with fact/operator/value entries. Facts use dot notation for nested keys.

{
  "all": [
    { "fact": "response.code", "operator": "greater_or_equal", "value": 200 },
    { "any": [
      { "fact": "action", "operator": "equal", "value": "opened" },
      { "fact": "action", "operator": "equal", "value": "reopened" }
    ]}
  ]
}

Evaluates conditions against the payload. Routes to transformation or task queue based on result:

• Condition passes + transformation present: routes to task.subtask.transform
• Condition passes + routing key present: routes to runner_routing_key
• Condition fails: conditioner.failed, no dispatch

• Exchange: task (inherits from Legion::Transport::Exchanges::Task)
• Queue: task.conditioner
• Routing keys: task.subtask, task.subtask.conditioner

• Ruby >= 3.4
• LegionIO framework (for AMQP actor mode)
• Standalone Client works without the framework

MIT