Page MenuHomePhabricator

Separate handle "status" and "availability"
ClosedPublic

Authored by epriestley on May 13 2015, 10:57 PM.
Tags
None
Referenced Files
F14017875: D12832.diff
Tue, Nov 5, 12:21 AM
F13994088: D12832.id30860.diff
Wed, Oct 23, 3:39 AM
F13984685: D12832.id.diff
Sun, Oct 20, 3:14 PM
F13959030: D12832.id30895.diff
Oct 14 2024, 5:32 PM
Unknown Object (File)
Oct 7 2024, 1:32 AM
Unknown Object (File)
Sep 17 2024, 8:14 AM
Unknown Object (File)
Sep 12 2024, 7:20 AM
Unknown Object (File)
Sep 12 2024, 7:20 AM
Subscribers

Details

Summary

Ref T7707. Handles currently have a "status" field and a "disabled" field.

The "status" field has these possible values: "open", "closed", "1", "2". durp durp durp

Instead, do:

  • status = <open, closed>
  • availability = <full, partial, none, disabled>

I think these make more sense? And are a bit more general? And use the same kind of constants for all values!

Test Plan

Looked at all affected handles in all states (probably).

Diff Detail

Repository
rP Phabricator
Branch
fxform13
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 5960
Build 5980: [Placeholder Plan] Wait for 30 Seconds

Event Timeline

epriestley retitled this revision from to Separate handle "status" and "availability".
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: btrahan.
epriestley edited edge metadata.
  • Look at more handles in more states.
src/applications/phid/PhabricatorObjectHandle.php
242–246

I suppose I could keep most of this around if it suits your fancy.

Oh, I guess getTextStatus() actually converts 1 and 2 into away and sporadic so they didn't actually make it to handles.

btrahan edited edge metadata.
This revision is now accepted and ready to land.May 14 2015, 5:40 PM
This revision was automatically updated to reflect the committed changes.