Page MenuHomePhabricator

Replace the informal "array" subtype map with a more formal "SubtypeMap" object
ClosedPublic

Authored by epriestley on Dec 6 2018, 4:15 PM.
Tags
None
Referenced Files
F19266438: D19852.diff
Mon, Dec 22, 8:06 PM
F19098669: D19852.diff
Thu, Dec 4, 5:26 PM
F18928592: D19852.id.diff
Nov 9 2025, 10:00 PM
F18868080: D19852.id.diff
Nov 4 2025, 4:31 AM
F18866681: D19852.diff
Nov 3 2025, 6:38 PM
F18863750: D19852.id47406.diff
Nov 3 2025, 12:57 AM
F18782213: D19852.id47411.diff
Oct 13 2025, 12:56 AM
F18749543: D19852.id.diff
Oct 4 2025, 4:13 AM
Subscribers
None

Details

Summary

Ref T13222. Ref T12588. See PHI683. To make "Create Subtask..." fancier, we need slightly more logic around subtype maps. Upgrade the plain old array into a proper object so it can have relevant methods, notably "get a list of valid child subtypes for some parent subtype".

Test Plan

Created and edited tasks, changed task subtypes. Grepped for affected symbols (newEditEngineSubtypeMap, newSubtypeMap).

Diff Detail

Repository
rP Phabricator
Branch
subtype1
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 21257
Build 28916: Run Core Tests
Build 28915: arc lint + arc unit