Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upConditionally Execute Rules in a Tree Structure #208
Comments
|
Hi @CacheControl, Did you get a chance to look at this request? Would appreciate your thoughts here. |
|
For Organization: For performance, |
|
@ozanerturk Each rule would have a different event. The Yes, it would be possible to meet the same logical need by implementing the segmentation conditions in the first condition of each rule (within an However, the example above is a relatively simple one, where there are only 1 or two segmentation conditions. As the number of segmentation conditions grows, the number of rules grows exponentially and the number of conditions within each rule grows linearly. |
|
Hmm. isn't that seems like routing for you too? |
Hello again @CacheControl!
A recent feature I've been thinking about, that would be beneficial to my use case, is executing multiple rules in a tree structure. The idea is that there are a set of conditions which, when evaluated to true, would indicate the need to execute a particular group of rules.
This would be enormously helpful to us to better organize my rules, but also to improve performance by not executing many of the rules.
Below is the logical model of how I think about the rules:
Now, I could easily implement this a 7 rules that all execute each time, with the conditions added to each rule. All 7 rules would run and all 7 rules would have more conditions to evaluate. What I'd like to happen, is for the conditions in the diamond to only execute once, then either rules 1-3 or rules 4-7 to execute.
I'd also add that this should be nestable, as in this picture:
Is this a capability/feature you feel should be added to the engine, or is this something you feel should be done outside of the engine? I would be happy to do a PR to add the capability if you think it would be valuable, or have any guidance on how to add it.