Page MenuHomePhabricator

Add a skeleton for Calendar notifications
ClosedPublic

Authored by epriestley on Nov 1 2016, 4:35 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Mar 5, 5:00 AM
Unknown Object (File)
Feb 13 2024, 8:43 PM
Unknown Object (File)
Feb 13 2024, 8:43 PM
Unknown Object (File)
Feb 12 2024, 8:32 AM
Unknown Object (File)
Feb 6 2024, 3:48 PM
Unknown Object (File)
Feb 6 2024, 3:29 PM
Unknown Object (File)
Feb 3 2024, 12:39 PM
Unknown Object (File)
Jan 26 2024, 8:59 AM
Subscribers
None

Details

Summary

Ref T7931. I'm going to do this separate from existing infrastructure because:

  • events start at different times for different users;
  • I like the idea of being able to batch stuff (send one email about several upcoming events);
  • triggering on ghost/recurring events is a real complicated mess.

This puts a skeleton in place that finds all the events we need to notify about and writes some silly example bodies to stdout, marking that we notified users so they don't get notified again.

Test Plan

Ran bin/calendar notify, got a "great" notification in the command output.

Screen Shot 2016-10-31 at 6.13.41 PM.png (109×341 px, 11 KB)

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Add a skeleton for Calendar notifications.
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.Nov 1 2016, 5:34 PM
This revision was automatically updated to reflect the committed changes.