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
Unknown Object (File)
Wed, Mar 20, 10:51 AM
Unknown Object (File)
Tue, Mar 19, 10:53 PM
Unknown Object (File)
Tue, Mar 19, 10:53 PM
Unknown Object (File)
Tue, Mar 19, 10:52 PM
Unknown Object (File)
Tue, Mar 19, 10:52 PM
Unknown Object (File)
Feb 16 2024, 2:06 PM
Unknown Object (File)
Feb 4 2024, 7:50 AM
Unknown Object (File)
Feb 3 2024, 8:06 PM
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
Lint
Lint Not Applicable
Unit
Tests Not Applicable