Include reasoning logic when restricting db #767
Conversation
|
This is meant to solve Story 1 from fluree/core#102 |
Accepts a rules graph with :reasoner-rules in the opts and a rules db with :reasoner-rules-db. Both of these keys expect a list, but since our reasoner only supports one rule source currently, the list should only have one element. If both a graph and a db are provided, it will use the db.
|
If anyone has ideas on how to get a db of rules from just an alias when using |
| db) | ||
| time-travel-db (-> (if t | ||
| (<? (time-travel/as-of policy-db t)) | ||
| policy-db)) |
There was a problem hiding this comment.
Love these more descriptive var names!
There was a problem hiding this comment.
With the new policy PR, this has changed a little bit so the above wouldn't be compatible. Now you compose dbs, instead of a bunch of if conditions in the API. In this case if you wanted a db to be policy-wrapped, you'd call that API first explicitly. This no longer looks for this option in a regular query.
Also if a query is wrapped in a verifiable credential, there is a new explity query API for that... so this check won't be done always.
There was a problem hiding this comment.
It looks like that PR has failing checks, should I wait for it to be merged and then adjust this PR to work with it?
No description provided.