Page MenuHomePhabricator

Use transactions when importing events in Calendar, and update existing events
ClosedPublic

Authored by epriestley on Oct 13 2016, 3:04 PM.
Tags
None
Referenced Files
F15444164: D16701.id40208.diff
Thu, Mar 27, 8:14 AM
F15437747: D16701.id.diff
Tue, Mar 25, 9:16 PM
F15437285: D16701.id40204.diff
Tue, Mar 25, 6:44 PM
F15434600: D16701.id40204.diff
Tue, Mar 25, 4:37 AM
F15430684: D16701.diff
Mon, Mar 24, 8:33 AM
F15419381: D16701.diff
Fri, Mar 21, 5:47 AM
F15345358: D16701.diff
Mar 10 2025, 10:05 AM
F15287379: D16701.id40204.diff
Mar 4 2025, 7:46 PM
Subscribers
None

Details

Summary

Ref T10747.

  • Apply what changes we can with transactions, so you can see how an event has changed and import actions are more explicit.
    • I'll hide these from email/feed soon: I want them to appear on the event, but not generate notifications, since that could be especially annoying for automated events.
  • When importing, try to update existing events if we can.
Test Plan

Imported a ".ics" file several times with minor changes, saw them reflected in the UI with transactions.

Screen Shot 2016-10-13 at 8.00.54 AM.png (502×755 px, 71 KB)

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Use transactions when importing events in Calendar, and update existing events.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
chad edited edge metadata.
This revision is now accepted and ready to land.Oct 13 2016, 3:52 PM
This revision was automatically updated to reflect the committed changes.