Page MenuHomePhabricator

When an object which supports subtypes is created, set its subtype to the creating form's subtype

Authored by epriestley on Mar 2 2017, 12:40 AM.
Referenced Files
Fri, Jun 24, 4:09 PM
Unknown Object (File)
Wed, Jun 22, 11:31 AM
Unknown Object (File)
Mon, Jun 13, 6:54 PM
Unknown Object (File)
Sat, Jun 11, 9:21 AM
Unknown Object (File)
Sat, Jun 11, 12:42 AM
Unknown Object (File)
Wed, Jun 8, 8:05 PM
Unknown Object (File)
Wed, Jun 8, 12:46 PM
Unknown Object (File)
Sat, Jun 4, 8:11 PM



Ref T12314. If you set a form to have the "plant" subtype, then create a task with it, save "plant" as the task subtype.

For Conduit, the default subtype is used by default, but a new "subtype" transaction is exposed. You can apply this transaction at create time to create an object of a certain subtype, or at any later time to change the subtype of an object.

This still doesn't do anything particularly useful or interesting.

Test Plan
  • Created a non-subtyped object (a Paste).
  • Created "task" and "plant" tasks via different forms.
  • Created "default" and "plant" tasks via Conduit.
  • Changed the subtype of a task via Conduit.
  • Tried to set a bad subtype.

Screen Shot 2017-03-01 at 4.34.06 PM.png (305×883 px, 36 KB)

Screen Shot 2017-03-01 at 4.34.44 PM.png (562×837 px, 85 KB)

Diff Detail

rP Phabricator
Lint Not Applicable
Tests Not Applicable