cultcache-ts: a pushAll through a dangling link is refused like push, not replaced #147
Loading…
Reference in a new issue
No description provided.
Delete branch "hands/ts-pushall-dangling"
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?
Follow-up
variants:follow_up:writer-dangling-link-tolerance: the reader owns the verdict on what is at the path, so the writer's tolerant branch goes.Rust already refuses (
a_push_all_through_a_dangling_link_is_refused_like_push_and_writes_nothing), as do C# and Python; TSpushAllwas the outlier, catching the reader's ENOENT and replacing the link. The R3 test that pinned the replacement now pins the refusal (failed first: 'Missing expected rejection'); the catch is deleted. Documented as a Breaking line in the cultcache-ts changelog Unreleased.cultcache-ts
npm test: 233 pass, 13 fail, the same 13 as main in the Mind sandbox (cross-runtime interop and browser bundle need cargo/dotnet/esbuild).🤖 Generated with Claude Code