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
We've been recently exploring switching from LearningLocker to OpenLRS. I was wondering if there is a reason why there is no XApiContext in XApiObject class. Is this deliberate? We found it useful in case where we've got XApiObjectType == SubStatement to be able to put the context of that SubStatement into the object when it came to using xApi for plans and planning. Creating 2 statements (StatementRef - planned, and target statement) creates querying overhead and if the StatementRef statement was lost there is no way of telling what the target statement meant.
Hello,
We've been recently exploring switching from LearningLocker to OpenLRS. I was wondering if there is a reason why there is no XApiContext in XApiObject class. Is this deliberate? We found it useful in case where we've got XApiObjectType == SubStatement to be able to put the context of that SubStatement into the object when it came to using xApi for plans and planning. Creating 2 statements (StatementRef - planned, and target statement) creates querying overhead and if the StatementRef statement was lost there is no way of telling what the target statement meant.
Thank you,
Chris