You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've looked across the documentation, examples and existing issues and, if this has been previously discussed, I'm missing it. Is it possible to use one or more Fact as params input to another fact?
This is a little domain specific but, for example, if I have a fact that gets a "section" related to another object (via params) and then another fact that verifies "section" access control, can I do something like this as a fact?
{// Has permission to section?fact: 'has-permission',params: {fact: 'related-section',params: {id: 'xyz123'}},operator: 'equal',value: true}
The text was updated successfully, but these errors were encountered:
I could do this right now by creating another new bespoke 'has-related-section-permission` fact which depends on 'related-section' from the almanac and then checks permissions. But this is is not ideal because it doesn't promote fully decomposing and reusing Facts on Rules.
@robross0606 one of the soon things on my wishlist is the ability to add a custom alamanc that would let you add functionality to as deeply as you would like do this.
I've looked across the documentation, examples and existing issues and, if this has been previously discussed, I'm missing it. Is it possible to use one or more Fact as
params
input to another fact?This is a little domain specific but, for example, if I have a fact that gets a "section" related to another object (via
params
) and then another fact that verifies "section" access control, can I do something like this as a fact?The text was updated successfully, but these errors were encountered: