User Details
- User Since
- Feb 21 2012, 9:22 PM (766 w, 1 d)
- Availability
- Available
Feb 5 2019
Nov 20 2018
Jan 8 2018
Dec 7 2017
Dec 5 2017
Dec 3 2017
Nov 30 2017
Nov 28 2017
@epriestley what do you think of creating another column in the calendar_eventinvitee table, something like a bool futureStatus so that when we get a list of invitees back, we can check for that flag. I think this would mean a lot of date comparisons (seems inefficient), and I'm not quite sure when to populate event stubs. For example, if the futureStatus flag is set to true for instance 10, and there are stubs for instances 15 and 20, when would 15 and 20 get converted to have the updated status?
Aug 25 2017
Mar 28 2017
Feb 12 2017
Feb 3 2017
Feb 2 2017
Nov 29 2016
Nov 3 2016
May 23 2016
May 5 2016
Apr 21 2016
Apr 20 2016
A few possible directions:
Yeah, I think the dialog should clarify.
I just think it might not look pretty on standard resolutions (like my Mac)
Alternatively, we can make reinstating a series un-cancel all cancelled instances. That would make some sense to me.
"Cancel All Recurrences" works because it will keep already cancelled instances that way. When you reinstate the series, all the individually cancelled instances won't be un-cancelled, so "Reinstate All Instances" doesn't really cover it. It should be more like "Reinstate All Previously Un-cancelled Instances". How would we put that succinctly?
Apr 15 2016
Apr 14 2016
Apr 13 2016
Apr 11 2016
Apr 9 2016
Apr 7 2016
Apr 5 2016
I expect two more diffs for this task: one for awarding/revoking badges in the badges.edit API call, and one for querying who awarded whom.
Apr 4 2016
Yeah, I was pondering the award/revoke flow. PasteEditConduitAPIMethod is so bare bones as an example, and PhabricatorBadgesEditEngine is so different from other edit engines... I'm just not sure how that will hook into the badges edit API method.
Is there a reason, other than scope, why we're not implementing a badges.create Conduit API method? Or any of the other ones?
Apr 3 2016
What's left is adding Awarded by ... to recipient list on badge view:
Apr 2 2016
Apr 1 2016
We currently track awarderPHID in the badges_award table. Do we still need an awarderPHID in badges_badge table?
Haha. Yes, well, you claim in another file that it was WoW colors. Get your story straight, @chad !
Did I get the colors wrong? I thought I copied them as they were...
Mar 31 2016
Mar 30 2016
This is done. Minor followup: T10698.
Mar 29 2016
How do I reproduce this error?
Mar 28 2016
Closing this, because it seems to be done, the way the title is written. All other related plans have their own tasks.
Pretty sure I covered all the badge transactions.