version 7 - Design
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 20/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- javascript
- 领域
- backend
调研方向
这是一个版本 7 的设计讨论,而不是实现任务,其中没有指定任何文件、测试或入口点。请先查看当前的 6.x 规则引擎以及讨论中引用的相关 Issue;要完成这项工作,需要就可扩展性、结构、Facts、Almanac、Conditions、Rules 和 Engine 达成一致的设计。
由索引模型根据 Issue 内容生成。
描述
Starting a thread here to put notes on a version 7 design.
Version 7 is an opportunity to make a number of changes that have been suggested in issues filed here that would make the JSON rules engine more extensible at the cost of breaking backwards compatibility with the current 6.x versions.
Extensibility vs. Structure
With version 7 we want to consider the tradeoff between extensibility and having a known structure. For instance introducing the ability to add custom Condition classes or custom Rule subclasses allows for the system to be highly extensible but makes it much harder to reason about the input and output of the rules engine without knowing about all these extensions.
Ultimately we need to draw this line somewhere and my initial inclination is to draw it in favor of more extensibility in order to allow the broadest possible use of the rules engine.
Concepts
Starting from a clean stale the following basic concepts will be part of the rules engine
Facts
Facts are things that are known by the rules engine during execution.
Almanac
The Almanac is the system for storing and looking up Facts.
Conditions
Conditions are executable, contain a priority, and return a result containing a boolean value. Generally there are 2 types of conditions, comparison conditions which check the value of a fact against another value, and composite conditions like all, any, and not which use 1 or more nested conditions to produce a result. By being fully extensible it's possible to introduce other types of conditions.
Rules
Rules are also executable and contain a priority. They generally are comprised of a set of conditions which are executed. Rules produce events as a result of execution.
Engine
The engine provides the mechanism to evaluate rules, and conditions. It includes mechanisms to resolve the values of facts or other special objects. Changing the engine can significantly change the behavior of the system.
- 主要语言
- JavaScript
- 星标
- 3.1k
- 派生
- 507
- PR 合并指标
- 30 天内没有已合并 PR
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
CacheControl/json-rules-engine 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 35/100
CacheControl/json-rules-engine#427 · 1 个 reaction ·
-
难度 4/5 3-5 天 新手友好度 35/100
-
难度 3/5 1-2 天 新手友好度 48/100
CacheControl/json-rules-engine#424 · 1 条评论 ·
-
难度 3/5 1-2 天 新手友好度 25/100
CacheControl/json-rules-engine#421 · 1 条评论 ·
-
难度 3/5 1-2 天 新手友好度 38/100
CacheControl/json-rules-engine#417 · 1 个 reaction ·
查看 CacheControl/json-rules-engine 的全部 Issue
相似的 Issue
-
curation good first issue
难度 2/5 1-3 小时 新手友好度 88/100
amponce/archive-movie-browser#186 ·
-
难度 2/5 1-3 小时 新手友好度 86/100
clerk/javascript#9852 ·
-
bug p1 tools
难度 2/5 1-3 小时 新手友好度 78/100
-
难度 2/5 1-3 小时 新手友好度 88/100
HarperFast/skills#96 ·
-
factory-active factory-automatic task-bug-reproduction-cannot-reproduce task-identify-harness-labels-done task-identify-issue-type-done
难度 2/5 1-3 小时 新手友好度 84/100