Giters
CacheControl
/
json-rules-engine
A rules engine expressed in JSON
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
2492
Watchers:
72
Issues:
250
Forks:
450
CacheControl/json-rules-engine Issues
Is the project providing an official JSON Schema to validate rules edition?
Updated
2 months ago
Slow performance while having large array of facts.
Updated
3 months ago
Comments count
9
Rule Evaluation taking around 10,000-15,000 ms for around 10k rules.
Updated
3 months ago
Use fact as params input to another fact?
Updated
3 months ago
Comments count
3
BigInt value is not working
Updated
4 months ago
Accessing Event on a Rule
Updated
4 months ago
Comments count
2
How to create multiple 'aggregate' facts on a 'parent' object calculated from child objects (composition)
Updated
5 months ago
Ability to stop rules execution after success for array of inputs
Updated
6 months ago
Complex rule for the fact
Updated
7 months ago
Comments count
2
Parent child rule
Updated
8 months ago
RuleResult class missing from type declarations
Updated
8 months ago
Comments count
1
What the best way to launch the rule engine
Updated
8 months ago
Handle error thrown by fact
Updated
9 months ago
Comments count
4
Example issue - undefined parameter
Closed
9 months ago
Comments count
1
problems with the execution of my rules
Closed
9 months ago
Comments count
4
Uncaught TypeError: (0 , _hashIt2.default) is not a function
Updated
9 months ago
Comments count
8
Error: Cannot find module 'lodash'
Closed
9 months ago
Comments count
1
Operator availability - between operator
Updated
9 months ago
Comments count
1
updateRule not working
Updated
9 months ago
Right side of Rule condition Fact comparison does not appear in Condition result
Updated
9 months ago
Declarative way for compute facts
Updated
9 months ago
Type of `Engine.on()` is wrong
Updated
9 months ago
Comments count
1
Ability to specify different events for failure and success
Updated
9 months ago
Comments count
1
Inclue RHS factResult after condition evaluation
Updated
9 months ago
Comments count
2
Is it possible to make sure that a fact triggers at most one rule?
Closed
10 months ago
Comments count
2
Feat: Type-safety using a FactTypeMapping
Updated
10 months ago
Comments count
1
Boolean operations(NOT) is not available
Closed
10 months ago
Comments count
2
is this project still active
Closed
a year ago
Comments count
9
Small error in docs
Closed
a year ago
Comments count
1
woops
Closed
a year ago
Comments count
1
How to feed engine multiple facts as array!
Closed
a year ago
Comments count
1
OnSuccess/OnFailure properties as part of the rule - Security Issue
Updated
2 years ago
Not able to resolve JsonPath when it includes a where condition
Updated
2 years ago
Comments count
1
Adding path values to events
Closed
2 years ago
Comments count
2
Caching issue with engine
Closed
2 years ago
Comments count
1
Condition for checking param is not falsy?
Updated
2 years ago
Comments count
1
Possible to use a rule as a fact in another rule?
Updated
2 years ago
Comments count
1
Cannot convert object to primitive value
Updated
2 years ago
Comments count
1
Find unused facts
Updated
2 years ago
How to extract all and any from JSON and parse them into expressions?
Updated
2 years ago
Rule chaining not working with Promise.all
Updated
2 years ago
Comments count
1
Is there a way to get all fact values either as part of event or as part of almanac?
Updated
2 years ago
Question - is there a way to clear all engine rules in a single command? or a way to
Updated
2 years ago
Check for conflict condition
Updated
2 years ago
Clarification on the node DEBUG example
Closed
2 years ago
Comments count
3
Fact results in event message?
Updated
2 years ago
PATH is not resolving correctly
Updated
2 years ago
Comments count
3
Using fact values in event parameters
Closed
2 years ago
Comments count
1
Checking for empty array on fact
Updated
3 years ago
Comments count
1
Convert rules to elastic search query
Updated
3 years ago
Previous
Next