PersistentHistoryTrackingKit 2.2.0
This release adds an observer-only processing mode for apps that want to use persistent history observation without letting the kit merge transactions into contexts.
What's New
- Added
TransactionMergeBehavior..automatickeeps the existing behavior: run Merge Hooks, then default merge when the hook pipeline continues..disabledskips the entire merge phase, including registered Merge Hooks and the default merge.
- Added
mergeBehaviortoPersistentHistoryTrackingKit.init, defaulting to.automaticfor source compatibility. - In
.disabledmode, Observer Hooks still run, the current author's timestamp still advances, and cleanup still followscleanStrategy. - Registering a Merge Hook while merge is disabled now emits a
.noticelog to make the inactive configuration visible.
Documentation
- README, READMECN, and Hook Mechanism docs now describe observer-only mode.
- Documentation clarifies that processed counts in
.disabledmode mean transactions were observed and timestamped, not merged into contexts. - Cleanup guidance now calls out the extra responsibility when cleanup is enabled while merge is disabled.
Compatibility
- Existing initializers continue to compile because
mergeBehaviordefaults to.automatic. - No changes to
.automaticmerge behavior are intended.