Page MenuHomePhabricator

Implement BYSETPOS for YEARLY and MONTHLY RRULES
ClosedPublic

Authored by epriestley on Sep 28 2016, 2:18 AM.
Tags
None
Referenced Files
F15507614: D16617.diff
Tue, Apr 15, 9:42 PM
F15490897: D16617.id39991.diff
Fri, Apr 11, 9:33 PM
F15467375: D16617.id40007.diff
Thu, Apr 3, 2:13 PM
F15412028: D16617.id39991.diff
Mar 19 2025, 10:55 AM
F15411957: D16617.id40007.diff
Mar 19 2025, 10:30 AM
F15392450: D16617.id.diff
Mar 15 2025, 3:17 PM
F15392417: D16617.diff
Mar 15 2025, 3:06 PM
F15385663: D16617.id40007.diff
Mar 14 2025, 11:05 PM
Subscribers
None

Details

Summary

Ref T10747. I may come back and try to clean this up, but at least make all the tests pass.

This stuff is really messy because if you have a YEARLY rule like "the 3rd of every month", and BYSETPOS on it, and the first instance is in June, too bad: we have to build every event for the whole year to apply BYSETPOS.

Test Plan

Unit tests now pass.

Diff Detail

Repository
rPHU libphutil
Branch
cal15
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 13880
Build 17968: Run Core Tests
Build 17967: arc lint + arc unit

Event Timeline

epriestley retitled this revision from to Implement BYSETPOS for YEARLY and MONTHLY RRULES.
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.Sep 28 2016, 2:27 AM
This revision was automatically updated to reflect the committed changes.