feat
BREAKING
task/move-delete-to-address
#1 / 1
feat: DELETE rows for move-sources carry to_address in op_payload
_diff_manifests now emits a delete tuple with to_address (the destination path) for every unambiguous move source, instead of silently suppressing it. The backfill loop writes that into op_payload so the semantic is persisted.
Template surfaces this as '↻ moved → <new-path>' (linked) on DELETE entries that carry to_address, using the purple --moved variant of sym2-new-version.
Also adds deploy/backfill_move_to_address.py to patch existing rows that were written before this change (finds MOVE rows, derives their DELETE counterparts, and writes to_address into op_payload or creates the row).
sha256:0e7310c3b3492e7ee99d9a0e87c4591191afce4a629228f630f9fd69088e0fb0
sha
+16
~4
symbols
sha256:80928a8cd04f1cbc68d279c615ef33bedc193519f7fdac67b2db11f95889d172
snapshot
+16
symbols added
~4
symbols modified
0
dead code introduced
Semantic Changes
20 symbols
+
test_diff_manifests_ambiguous_delete_has_no_to_address
method
method test_diff_manifests_ambiguous_delete_has_no_to_address L2147–2161
+
test_diff_manifests_move_emits_delete_with_to_address
method
method test_diff_manifests_move_emits_delete_with_to_address L2131–2145
+
test_move_delete_op_payload_has_to_address
method
async_method test_move_delete_op_payload_has_to_address L2164–2194
← Older
Oldest on task/move-delete-to-address
All commits
Newer →
Latest on task/move-delete-to-address
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:0e7310c3b3492e7ee99d9a0e87c4591191afce4a629228f630f9fd69088e0fb0 --body "your comment"
No comments yet. Be the first to start the discussion.