Repository navigation
Epic: Sharing, invites and collaboration depth #54
Description
Summary
The app ships share-links, list watchers and document collaborators. What it is missing is the invite-by-email path (which the web now leads with), the claim/resolve side of a share link, and the role/notification controls around an invite.
Unimplemented endpoints
| Method | Path |
|---|---|
GET/POST |
/api/lists/{id}/invites |
DELETE |
/api/lists/{id}/invites/{token} |
GET/POST |
/api/lists/invite/{token} |
GET/POST |
/api/lists/shared/{token} |
GET |
/api/lists/shared/{token}/data |
GET/POST |
/api/documents/{id}/invites |
DELETE |
/api/documents/{id}/invites/{token} |
GET/POST |
/api/documents/invite/{token} |
GET/POST |
/api/documents/shared/{token} |
Live verification (2026-09-15)
GET /api/lists/{id}/invites -> 200 {"invites":[]}
Product behaviour (/help/documents)
The Share window leads with "Invite people" — the way to give specific people access while the item stays private — and offers Make public as a secondary option below. The public toggle was removed from the editor and now lives only in the Share window. Inviting (and changing a role) is a subscriber feature, but the people invited never need to pay — granted access is free at whatever level was chosen.
Repo conventions to follow
- Service: one
partial class InterlinedApiClientfile per domain inInterlinedList/Services/. - Wire types in
InterlinedList/Models/matching real API JSON. - ViewModel per view in
InterlinedList/ViewModels/(CommunityToolkit.MvvmObservableObject+[RelayCommand]). - View is a self-contained
UserControlinInterlinedList/Views/that news up its own VM fromAppServices.Session. - Strata tokens only — no colors/fonts/radii outside
Resources/Palette.xaml+Theme.*.xaml. - Read-after-write for any mutating endpoint whose response envelope has not been live-verified.
Activity