Page MenuHomePhabricator

T5464, ApplicationTransactions for calendar events
ClosedPublic

Authored by lpriestley on Apr 28 2015, 4:17 AM.
Tags
None
Referenced Files
F14031525: D12586.id30224.diff
Sat, Nov 9, 11:01 AM
F14031523: D12586.id30225.diff
Sat, Nov 9, 11:01 AM
F14031522: D12586.id30220.diff
Sat, Nov 9, 11:01 AM
F14028607: D12586.id30225.diff
Fri, Nov 8, 2:30 PM
F14021610: D12586.id30225.diff
Wed, Nov 6, 10:07 AM
F14000808: D12586.id30220.diff
Fri, Oct 25, 1:13 AM
F13997380: D12586.diff
Thu, Oct 24, 4:05 AM
F13989640: D12586.id30225.diff
Mon, Oct 21, 9:57 PM

Details

Summary

Closes T5464, Implement ApplicationTransactions in Calendar.

Test Plan

Create a calendar event, update calendar event, detail view of event should show update history.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

lpriestley retitled this revision from to T5464, ApplicationTransactions for calendar events.
lpriestley updated this object.
lpriestley edited the test plan for this revision. (Show Details)
lpriestley added a reviewer: epriestley.
epriestley edited edge metadata.

Couple of minor inlines. Also:

  • Looks like the .sql files didn't get added -- maybe a weird ~/.gitignore rule?
src/applications/calendar/controller/PhabricatorCalendarEventEditController.php
103

For consistency, prefer getID() over getId().

src/applications/calendar/editor/PhabricatorCalendarEventEditor.php
105–107

Just remove this stuff for now.

src/applications/calendar/storage/PhabricatorCalendarEventTransaction.php
12–15

These probably shouldn't be four separate mail tags. Mail tags are used to offer preferences in SettingsEmail Preferences so users can get email about more important events (like a task being opened or closed or commented on) but not be emailed about less important events (like priority changes or project adjustments).

It doesn't seem very useful to set different preferences for the start and end times of an event. Even though "start time" is arguably a bit more important than "end time", I'd guess that almost all users probably always want to be notified in the same way about any scheduling change. I'd maybe provide two tags here instead:

  • MAILTAG_CONTENT - The content of an event changes (start date, end date, description).
  • MAILTAG_OTHER - Other information about an event changes (status).
26

Should be PhabricatorCalendarEventTransactionComment.

This revision now requires changes to proceed.Apr 28 2015, 10:53 AM
lpriestley edited edge metadata.
lpriestley marked 4 inline comments as done.

Addressing code review and adding fixed the sql .gitignore rule.

epriestley edited edge metadata.
epriestley added inline comments.
src/applications/calendar/storage/PhabricatorCalendarEventTransaction.php
24

Then add "Event" here too.

196–206

This still uses the old tag constants.

src/applications/calendar/storage/PhabricatorCalendarTransactionComment.php
3 ↗(On Diff #30224)

Oh, this should be PhabricatorCalendarEventTransactionComment for consistency with the Transaction class and the table name (that is, add "Event").

This revision now requires changes to proceed.Apr 28 2015, 1:07 PM
lpriestley edited edge metadata.
lpriestley marked 3 inline comments as done.

Renaming PhabricatorCalendarTransactionComment.php to PhabricatorCalendarEventTransactionComment.php

This revision is now accepted and ready to land.Apr 28 2015, 1:22 PM
This revision was automatically updated to reflect the committed changes.