Skip to content

docs(glue): an expansion's rows do not outlive their master #32

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
delchev wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(glue): an expansion's rows do not outlive their master #32

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/spec/glue.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -503,6 +503,18 @@ expansions:

A span change replaces the generated child set — never mix hand-entered rows into an expanded child.

::: info Normative
Deleting the master removes the rows the expansion generated for it. Only rows selected by the
expansion's own back-reference are removed, and each is removed through the child's layer, so the
child's delete event fires for every row and anything reacting to a deleted child reacts exactly as
it would for a hand-deleted one. The removal is idempotent.
:::

The generated rows are the expansion's, not the author's, and that is what settles the question:
without this rule they would be the one part of a deleted record that survives it — still pointing at
an id that no longer resolves, still counted by every roll-up, report and balance that counted them
while the record existed.

## generates — create-from

One-click "create a document from this document":
Expand Down