Download the PHP package kmuenkel/rule-evaluator without Composer
On this page you can find all versions of the php package kmuenkel/rule-evaluator. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download kmuenkel/rule-evaluator
More information about kmuenkel/rule-evaluator
Files in kmuenkel/rule-evaluator
Package rule-evaluator
Short Description Check a given data-set against a recursive rule-set
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package rule-evaluator
Rule Evaluator
Check a given data-set against a recursive rule-set
You begin with a config array that may or may not originate from a database. There are only three dataponts to each "rule".
- First Value
- Comparison operator
- Second Value
The key name for the first and second values indicates the nature of these values.
reference1/reference2indicates that the content will posses a dot-notation reference to a datapoint within the array of data being evaluated.value1/value2will expect to hold a static value that should be taken at face value.child1/child2means the "value" would be the boolean result of a nested "rule".
Through the dot-notation references and support of 'child' rules, both the data and the conditions support infinite complexity. But being a flat 3-point 'rule' record, this makes it conducive to the rules being managed through a database instead of a config file. While such a parser doesn't exist yet, all you'd need to do is ensure that your DBParser class implements the same Parser interface as the current ConfigParser.
The comparison operators, keyed as comparator, may be any of the following:
- '==': Value 1 equals value 2
- '===': Value 1 strictly equals value 2
- '!=': Value 1 does not equal value 2
- '!==': Value 1 strictly does not equal value 2
- '>': Value 1 is greater than value 2
- '<': Value 1 is less than value 2
- 'in': Value 1 can be found in an array defined as value 2
- 'not in': Value 1 cannot be found in an array defined as value 2
- 'and': Value 1 and value 2 must resolve to
true - '&&': Same as 'and'
- 'or': Value 1 or value 2 must resolve to
true - '||': Same as 'or'
- 'regex': Value 1 matches a pattern defined by value 2
- 'all':
- All elements in an array defined by value 1 must be found in an array defined by value 2
- Or If only one array is present, it must be reference nested rules that all resolve to
true
- 'any':
- Any element found in an array defined by value 1 must be found in an array defined by value 2
- Or If only one array is present, it must reerence nested rules, for which at least one resolves to
true
- 'none':
- None of the elements in an array defined by value 1 may be present in an array defined by value 2
- Or If only one array is present, it must reference nested rules that all resolve to
false(or be empty)
- 'passes': Value 1 and the entire dataset being evaluated get passed to a closure defgined by value 2, the output of which must resolve to
true. This allows for custom rules behavior to be added.
Sample Usage
ruleConfig.php
data.json
