Skip to content

Seating: a plus-one follows their guest into a family, and out of it - #95

Merged
JFrusher merged 1 commit into
mainfrom
feat/seating-plus-one-family
Oct 5, 2026
Merged

JFrusher merged 1 commit into
mainfrom
feat/seating-plus-one-family

Conversation

@JFrusher

@JFrusher JFrusher commented Oct 4, 2026

Copy link
Copy Markdown
Owner

Closes #62

What a user would notice

  • Add a guest to a family, and the person they bring (plusOneOf) joins too.
  • Take the guest out of the family, and their plus-one leaves with them.
  • Either way it is one command, so one undo puts both back.
  • A plus-one someone deliberately put in a different family stays where they were put.

How

  • plusOnesWith(plan, guest): the guests whose plusOneOf is this guest and who are in the same family as them (or, like them, in none).
  • addToFamily moves the guest and those plus-ones in a single command. Each move reads what the previous one wrote (family(), subgroup(), group()), so moving two people out of the same old family keeps both removals.
  • removeFromFamily takes the same set out together.

Dragging several selected guests onto a family still calls addToFamily once per guest. If both a guest and their plus-one are selected, the second call is a no-op on membership.

Checks

  • New tests in store/organise.test.ts: follows in; follows from one family to another; stays in a different family; leaves with their guest. Three failed on main; the "stays" case passed on main and still does. All pass now.
  • Seating unit tests, typecheck: green. e2e as listed in the batch: 61/61.

🤖 Generated with Claude Code

https://claude.ai/code/session_01VhFp1PtVBwgmxST9ZrRTEs


Generated by Claude Code

…of it

Adding a guest to a family left the person they bring behind, so every
couple had to be added one at a time and a plus-one could end up split from
their guest. The plus-one now comes too, in the same command, so one undo
puts both back. Taking the guest out of the family takes their plus-one
with them.

A plus-one someone deliberately put in a different family stays there.

Closes #62

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VhFp1PtVBwgmxST9ZrRTEs
@vercel

vercel Bot commented Oct 4, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
knotwork-suite Ready Ready Preview Oct 4, 2026 7:47pm UTC

@JFrusher
JFrusher merged commit 1515e7f into main Oct 5, 2026
10 checks passed
@JFrusher
JFrusher deleted the feat/seating-plus-one-family branch October 5, 2026 06:41

This branch was successfully deployed

1 active deployment
Preview — eeab5da2 Deployed Oct 4, 2026 by vercel[bot]
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.

A plus-one should follow their guest into a family

2 participants