Alternate names, self-person link, deletion integrity + dangling people #20
Reference in New Issue
Block a user
Delete Branch "names-deletion-self"
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?
Stacked on #19.
45 backend tests pass; migration up/down verified; frontend builds.
Names (the genealogy standard: maiden name primary, married/alias as typed alternates): - Name model already supported multiple typed names; expose full CRUD — NameCreate/Read/Update schemas, name_service (one-primary invariant, promote-on-delete), nested /persons/{id}/names routes. - Person page gains a Names card: add/edit/delete + "make primary", with a curated name_type dropdown (birth/maiden, married, alias, nickname, …). Self-person ("who am I"): - users.self_person_id FK (use_alter for the users<->persons<->trees cycle) + migration; PATCH /users/me/self-person; "This is me" / "This is you" on the person page. Soft-deleting the linked person clears it. Deletion integrity (fixes the broken tree view): - delete_person now soft-deletes the relationships touching the person, so no dangling edges remain; family-chart also filters links to missing people. - Optional cascade=true recursively deletes descendants (GEDCOM cleanup); the person page asks "only this person" vs "with all descendants". - DELETE returns {deleted: n}. Family view surfaces "Not connected to anyone" so dangling people aren't lost. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>