From fe142bbd3af1275d70a71a7053f298e424116a98 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marc-Andr=C3=A9=20Bombeck?= Date: Mon, 3 Aug 2026 10:20:26 +0200 Subject: [PATCH] Correct the entry type's account of what a level is The payload type still said the level is read throughout and `canWrite` false. Both were true of the shipped release and neither survives the invitation gaining a choice. Also says what `canWrite` does not mean, since the word invites a larger reading than the thing it grants. --- src/lib/sharing/account-access-view.ts | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/src/lib/sharing/account-access-view.ts b/src/lib/sharing/account-access-view.ts index 264e3693c..de0d06d0d 100644 --- a/src/lib/sharing/account-access-view.ts +++ b/src/lib/sharing/account-access-view.ts @@ -20,9 +20,13 @@ export interface AccountAccessEntry { accountId: string; username: string; displayName: string | null; - /** The grant's level. `"read"` throughout v1. */ + /** The grant's level, as the owner offered it and the caller accepted it. */ access: "read" | "write"; - /** May this caller change that record. Resolved server-side; `false` in v1. */ + /** + * May this caller ADD to that record. Resolved server-side. It never means + * edit or delete: those stay with the owner at both levels, and no field + * here offers them. + */ canWrite: boolean; }