Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve the closure execution backtracking. #11

Open
aitrusgit opened this issue Oct 5, 2017 · 0 comments
Open

Improve the closure execution backtracking. #11

aitrusgit opened this issue Oct 5, 2017 · 0 comments

Comments

@aitrusgit
Copy link
Contributor

Right now context is part of the result provided by the engine.process method. Such context holds a reference to all the rules that have been evaluated (only rules, not other closure types).

  1. Does it make sense to hold reference to ALL closures evaluated? The original reason for not going this way was to prevent very granular closures to flood the execution log. We can prevent that by only adding the closures that have certain special mark in the definition ( having a description? having a name?)

  2. In line with that we need to have a way for each rule (or closure) to reference their original definition (so things like, by example, description are not lost)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant