Consider coalescing core + flexible-field audit entries for a single edit #13
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Editing an object's core fields (
catalog::update_object) and its flexible fields (catalog::set_object_fields) are separate calls, each recording its ownUpdatedaudit entry. When the API layer (Plan 7+/10) performs one logical edit touching both, in one transaction, that yields two audit entries for what the user sees as a single change.Decide whether to coalesce them (e.g. a combined
edit_objectthat records one audit entry with the union of core + flexible diffs) or accept two entries. Not a problem at the repository layer today; surfaces when the API composes the two.Source: Plan 5 (object flexible fields) notes — forward-looking, an API-layer design decision.