-
Notifications
You must be signed in to change notification settings - Fork 181
-
Notifications
You must be signed in to change notification settings - Fork 181
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
Facts defined in compile options not available via getDefined() #23
Comments
I hadn't thought of this use case, typically if I have externally defined classes for the rules engine I will just require the module/file that contains them. However I can see where this would be useful. I will see about adding this in the next release. |
Thanks, Doug. I really appreciate the work you're doing with |
* Updated grunt * Fixed nextTick issues for node v0.10 noolsjs#32 * Added ability to remove a defined flow from nools. noolsjs#31 noolsjs#22 * Added ability to use `getDefined` on externally defined fact types. noolsjs#23 * Fixed all jshint issues * Rebuilt nools.js and nools.min.js * Added more tests for new globals feature
* Updated grunt * Fixed nextTick issues for node v0.10 noolsjs#32 * Added ability to remove a defined flow from nools. noolsjs#31 noolsjs#22 * Added ability to use `getDefined` on externally defined fact types. noolsjs#23 * Fixed all jshint issues * Rebuilt nools.js and nools.min.js * Added more tests for new globals feature
I think I should be able to do this:
custom-facts.js
custom-flow.js
But it seems that, event though the rules compile correctly, the classes are not available via
getDefined()
. It would be nice to have this work. I'd like to define my classes in coffeescript (in an separate file) and provide them to the rest of the app as if they were part of the rules file.Or am I approaching this wrong?
The text was updated successfully, but these errors were encountered: