json-rules-engine-simplified
json-rules-engine-simplified copied to clipboard
RXNT
A simple rules engine expressed in JSON
Changing required npm version so the package will work with future npm versions
I use this rule: ``` [{ "conditions": { "not": { "and": [{ "field_1": { "includes": ["opt1", "opt2"] } }] } }, "event": { "type": "remove", "params": { "field": "field_2" }...
The async nature of `.run` does not seem necessary. The function `applicableActions` does no asynchronous work, so it's really a promise for no reason. I wouldn't normally care, but I'm...
I have a use case where, I have to create rules for collections. ` var fact ={ Person:{ Name:"ricky", phoneNumber:"1234567890", areaCode:"EA_001" }, address:[ {streetName:"georgeSt", BuildingName:"SHORE Villa", flatNumber:"007, flag:"red"}, {streetName:"Hardy St",...
Follow up on https://github.com/RxNT/react-jsonschema-form-conditionals/issues/60 If match is done on an array, user might want to get indexes of matched array elements.
As described in #31 I found out, that the Test case is incomplete and indeed throws an error when correctly defined using a schema. The validation then seems to throw...
Hello, I am a little bit frustrated because I cannot explain what is happening here. Problem: extending predicate and then using the predicate in the conditions simply does not work....