Skip to content

docs: a roll-up recomputes on the child's update too - #31

Open
delchev wants to merge 1 commit into
mainfrom
docs/rollup-child-update
Open

docs: a roll-up recomputes on the child's update too#31
delchev wants to merge 1 commit into
mainfrom
docs/rollup-child-update

Conversation

@delchev

@delchev delchev commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

The rollups section of spec/glue.md stated the event set for the counting case only, and as create / delete — so an edit that moves a child to another parent recomputed neither counter.

Now stated once for every op (create, update and delete), with the re-parenting case spelled out: the parent a child moved to is corrected immediately; the parent it moved away from is not named by that event and converges the next time one of its own children changes.

Tracks spec proposal IntentFile/intent-specification#40. Built locally with npx vitepress build docs — clean.

🤖 Generated with Claude Code

The rollups page stated the event set for the counting case only, and as
create / delete - so an edit that moves a child to another parent recomputed
neither counter. Say it once for every op, and say what the update pass
buys: the parent a child moved to is corrected immediately, the one it left
converges on its next own change.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant