Repository navigation
Keep phone metadata when titles name automatic events - #122
Conversation
User requested checking unresolved comments with a focus on CodeRabbit, separate reviewable changes, and minimal shipped bytes. Extract phone metadata before applying the existing title-derived event name and cover the regression. Refs #107
| if (useTitle) { | ||
| event = theTitle; | ||
| } else { | ||
| if (!useTitle || type === "phone") { |
There was a problem hiding this comment.
Special-casing phone leaves the same metadata loss in place for the other three types: against the built script, a titled outbound/download link still sends no url and a titled mailto: link no email. Dropping the !useTitle || guard entirely (always run the switch, then let if (useTitle) event = theTitle; rename the event) fixes all four types and builds 19 minified / 10 gzip bytes smaller, at the cost of adding url/email metadata to titled links on existing installations.
Documentation update
|
Claude review checkpointReviewed commit |
|
SDLC label: |
Summary
Refs #107. Targets
v12for #40.titled tel: click retain title-derived event name + retain phone metadataUser steering: verify unresolved CodeRabbit findings, keep one change per PR, and minimize shipped bytes. Run the existing phone extraction even when the title supplies the event name; other event types retain their behavior.
Evidence
tel:+31201234567?extension=42withtitle="Call sales"sendsphone_Call_saleswithout phone metadata; the regression test fails.phone: "+31201234567"; 54 offline unit tests pass.Security implications
Titled phone events now contain the same phone metadata as untitled phone events. Query suffixes are excluded. Collection settings and phone event defaults remain as accepted for v12.
Merge Danger
Door: two-way
Blast Radius: phones
Checklist
Summary by CodeRabbit