Repository navigation
Permanent per-pair link for calendar events (#203) - #224
Merged
Merged
Conversation
A new route, /pair/{userIdA}/{userIdB}, opens the pair's open chain meeting,
whichever that is by now, so the link can sit in a recurring calendar event
and keep working after each archive. With no open meeting it shows the last
closed one and offers to schedule the next, with the colleague preselected
on the create form. A link to a pair the user isn't part of, or with no
shared meetings, gets a clear message.
The meeting page's header gets a "Calendar link" button that copies the
link, with a hint on where to paste it.
The URL names both people rather than the issue's proposed
/with/{counterpartUserId}: a counterpart-only link works for just one of the
two, and a recurring 1:1 is one shared calendar event. Frontend only.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #203, part of #213.
What
/pair/{userIdA}/{userIdB}— a pair's permanent link. It redirects to the pair's open chain meeting (one-offs ignored), so it keeps working after the meeting is archived and the next cycle starts.Frontend only: no new API, no schema change.
The issue's open questions
/with/{counterpartUserId}. A counterpart-only link works for just the person who copied it, while a recurring 1:1 is normally one shared calendar event with one description.pairPath()sorts the ids, so both participants get the same link.Beyond the issue
"Schedule the next one" preselects the colleague on the create form (an in-memory hand-over like "Create another");
UserTypeaheadnow shows a value set from outside.Left open
Both are listed in
docs/decisions/2026-10-03-pair-calendar-link.md:Verification
pairMeeting()(open over closed, most recent closed, next cycle after an archive, one-offs ignored, unknown user),pairCounterpartId(), the route, and the create-form hand-over.make verify-pr-readywas not run in full: no backend change.code-reviewrounds: round 1 led to the two-id URL, round 2 found a redirect that could fire after the page was left (fixed), round 3 came back clean.Translations for all 6 locales were written by Claude and are not native-speaker-reviewed.
🤖 Generated with Claude Code