Possible to use a rule as a fact in another rule?

Open
#305 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
28/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
backend

Research direction

The issue names no files, tests, or entry points. Start by locating the rule and fact evaluation paths, then clarify how a rule referenced as a fact should be evaluated; done means Rule 2 can reuse Rule 1 without duplicating Field A and existing behavior remains covered.

Written by the indexing model from the issue text.

Description

We're working on better decomposing our facts and rules, and have found that (due to our data model hierarchy), we're having to re-stipulate the same facts in multiple rules. Is it possible to use a rule as a fact in another rule so we can avoid having to copy/paste fact statements into multiple rules which is tedious and error prone?

For example, if Rule 1 states that FieldA must be true, and Rule 2 states that Field A must be true and Field B must be false, is it possible to construct Rule 2 such that Rule 1 must be true and Field B must be false?

Dominant language
JavaScript
Stars
3.1k
Forks
507
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CacheControl/json-rules-engine

All issues in CacheControl/json-rules-engine

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.