Description
Currently, grant/revoke permission actions append a log entry string nested in json permission log. Each log entry comprises semi-colon delimited variables, from which data is obtained by splitting and numeric indexing. The log entries need to be updated to a data model class written as json to allow them to be more easily and developed to record more expressive permissions if the log entry were instead written as a json data model.
From createPermLogEntry():
final logEntryId = DateFormat('yyyyMMddTHHmmssSSS').format(DateTime.now());
final logEntryStr =
'$dateTimeStr;$resourceUrl;$ownerWebId;$permissionType;$granterWebId;$recipientWebId;${permissionListStr.toLowerCase()}';
logEntry = LogEntry(id: logEntryId, record: logEntryStr);
Why
So that as a developer I can access data from the log entries more easily, and develop more features. Eg record other more expressive permissions, or create a searchable permission log history.
Closing Criteria
Checklist for closing the issue:
Description
Currently, grant/revoke permission actions append a log entry string nested in json permission log. Each log entry comprises semi-colon delimited variables, from which data is obtained by splitting and numeric indexing. The log entries need to be updated to a data model class written as json to allow them to be more easily and developed to record more expressive permissions if the log entry were instead written as a json data model.
From createPermLogEntry():
Why
So that as a developer I can access data from the log entries more easily, and develop more features. Eg record other more expressive permissions, or create a searchable permission log history.
Closing Criteria
Checklist for closing the issue:
make prepmake qtest