Users should be able to call up the next and previous occurrence of a fact until there aren't any more. In the UI we might put left and right arrows next to the fact being explained to allow this.
We should attempt implementing by scanning the event log on the server via a socket call and returning the log entry (we need to find the log entry to generate the explanation anyway).
The search should only proceed if we check the fact against the schema and it is not one-to-many.
Then we can use the e-a combination as the fact's identity / thing to search for.
Note: I think this is the right approach but we should eliminate piggiebacking on existing Precept client-side rules implementation for the search.
Users should be able to call up the next and previous occurrence of a fact until there aren't any more. In the UI we might put left and right arrows next to the fact being explained to allow this.
We should attempt implementing by scanning the event log on the server via a socket call and returning the log entry (we need to find the log entry to generate the explanation anyway).
The search should only proceed if we check the fact against the schema and it is not one-to-many. Then we can use the e-a combination as the fact's identity / thing to search for.
Note: I think this is the right approach but we should eliminate piggiebacking on existing Precept client-side rules implementation for the search.