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
The current patch element does not contain enough information to reverse the operation.
In version control it is important to be able to make incremental changes to a document, but it is also important to maintain an audit trail and to be able to reverse patches that have previously been applied. I am therefore proposing a method for creating audit records from the patch elements and how to create the reverse patch actions from an audit record, so you can go back to any previous state.
Details
The format of an audit record will look like this:
{
"timeStamp": "ISO 6801 timestamp for the action",
"previous": "Properties from the document or the patch before applying the patch element to assist in creating the reverse audit record. See examples below.",
"action": "The patch element"
}
For each operation, there is an equivalent reverse operation. This list below shows how they map:
Summary
The current patch element does not contain enough information to reverse the operation.
In version control it is important to be able to make incremental changes to a document, but it is also important to maintain an audit trail and to be able to reverse patches that have previously been applied. I am therefore proposing a method for creating audit records from the patch elements and how to create the reverse patch actions from an audit record, so you can go back to any previous state.
Details
The format of an audit record will look like this:
For each operation, there is an equivalent reverse operation. This list below shows how they map:
Examples
For the examples, I will be using this document:
add
The patch element:
Audit record:
Note: The "previous" property is not needed here.
Reverse patch element:
remove
The patch element:
Audit record:
Reverse patch element:
replace
move
copy
test
The text was updated successfully, but these errors were encountered: