Paul LütznerandClaude Opus 5.5 34f6ec5951 Read a recipient's name from the chip the app actually draws ...

Reported from the demo: a template inserted into a reply to Priya
Raman kept its "First name" placeholder, with her name in To.

recipientValues() parsed `Name (address)`. That is how
Contact::__toString() spells a contact, and it is not what the To
field shows: ContactAutocompleteField's choice_label writes
`Name <address>`. So no chip for a named contact ever parsed, and
neither the name nor — for those contacts — the address was filled
in. Only an address typed by hand worked, because that chip is the
bare address.

It now reads the angle-bracket form first and still accepts the
parenthesised one, and strips the quotes address syntax puts round a
name with a comma in it.

The browser test for this passed all along, because it wrote its own
chip label in the format the parser expected: it agreed with the code
and not with the app. It now uses the real format, and the reply test
asserts the first name of a recipient the SERVER put in To, which is
a label no test chooses.

The preview's sample recipient in the three catalogues was in the
same wrong format and is corrected with it.

Refs #26

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-09 15:09:06 +02:00

..

pending_cancel.js

fix(calendar): an event that runs over days says both of them

2026-08-27 18:33:51 +02:00

template_variables.js

Read a recipient's name from the chip the app actually draws

2026-10-09 15:09:06 +02:00