json-rules-engine

json-rules-engine copied to clipboard

Check rule conditions serially instead of in parallel

11

We're running into issues where our facts are based on transactional access to a database. When we try to properly decompose our rules into multiple facts, we hit problems where...

robross0606

Small error in docs

1

First of all great product. i think there is a small mistake in the coding if i am not mistaken it should be product.giftCard=== params.giftCard https://github.com/CacheControl/json-rules-engine/blob/90272d61ed7bea8b7d4000305511e932490d2e2e/examples/08-fact-comparison.js#L69

d-sooter

Is it possible to use the result of a fact in the fired event message for a rule? I've searched the documentation, examples and existing issues and not quite found...

robross0606

PATH is not resolving correctly

3

I have seen some strange happenings with regard to how the JSON-PATH is resolving in the rules with `"json-rules-engine": "6.1.2"`. If you consider the following rule: ```JSON { "ruleId": 1,...

mdebarros

Boolean operations(NOT) is not available

1

We need full support for NOT operators for arbitrary complexity

vinodhj

Ability to specify different events for failure and success

1

How can I return different event params depending on whether the rule succeeds or not? Thanks

carapai

Minor style edits. Thank you for this very helpful project! 👋

bertday

Is it possible make value as a dynamic data like using path?

3

**Example:** ``` conditions: { all: [{ fact: 'account-information', operator: 'equal', value: 'microsoft', // **Is it possible make this value 'microsoft' as a dynamic content?** path: '$.company' // access the 'company'...

intermx-reddysai

Async Operator

1

Is posible to have an async operator?

ctaity

Caching issue with engine

1

I am having a use case scenario where I have a very simple rule that is run against provided fact(s). When I run the engine, I notice that on success...

iprasla