makiolaj/calendula
1
0
Fork 1
Code Issues Pull Requests 6 Actions Releases 23 Activity

feat(edit): add guests from the contact picker
All checks were successful
Translations / check (pull_request) Successful in 28s
Details
CI / ci (pull_request) Successful in 9m19s
Details

Browse Source 
Close the name-on-manual-add gap. The add-guest row gains a "from
contacts" button that launches the system contact picker (ACTION_PICK on
ContactsContract Email URI); the picked email row is queried for
Email.ADDRESS + DISPLAY_NAME, so a chosen guest gets both email and name
in one tap. No READ_CONTACTS — the result Intent grants temporary read
access to just that row, so Calendula stays no-permission/no-network. The
inline email field remains the quick email-only path. Mark the roadmap
item shipped.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Jean-Luc Makiola
2026-06-22 23:50:23 +02:00
parent ac17343747
commit a4e0ec3fde
4 changed files with 79 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
.planning/ROADMAP.md
View File

@@ -490,15 +490,15 @@ detail screen (since v0.6) but the form can't write them. Make guests editable.
required/optional type updates; organizer/resource/no-email rows untouched).
Reminders restyled to the same grouped-list pattern in passing. Needs only the
existing `WRITE_CALENDAR` — no new permission.
- **Name on manual add — solved next via a contact picker.** The inline field is
email-only (the quick path); names otherwise come from sync. The planned fix is
a **"from contacts" entry**: `ACTION_PICK` on
`ContactsContract.CommonDataKinds.Email.CONTENT_URI` → the system Contacts app
returns a URI to the picked email row, queried for `Email.ADDRESS` **and** the
contact `DISPLAY_NAME`, so a picked guest gets both email and name directly. The
result Intent grants temporary read access, so **no `READ_CONTACTS` permission**
— one-shot and user-driven, same no-permission mechanism as the location address
picker above. Self/organizer rows stay non-editable.
- **Name on manual add — SHIPPED via a contact picker** (2026-06-22). The inline
field is email-only (the quick path); the add row also has a **"from contacts"
button**: `ACTION_PICK` on `ContactsContract.CommonDataKinds.Email.CONTENT_URI` →
the system Contacts app returns a URI to the picked email row, queried for
`Email.ADDRESS` **and** the contact `DISPLAY_NAME`, so a picked guest gets both
email and name in one tap. The result Intent grants temporary read access, so
**no `READ_CONTACTS` permission** — one-shot and user-driven, same no-permission
mechanism as the location address picker above. Self/organizer rows stay
non-editable.
- **Invitation behavior — DECIDED 2026-06-22: record-only, all writable
calendars.** Calendula has no INTERNET and never sends an invitation itself; it
only writes `Attendees` rows. Whether a guest is notified is decided downstream: