Page MenuHomePhabricator

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

Authored by epriestley on Mar 2 2017, 12:40 AM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Oct 9, 12:21 AM
Unknown Object (File)
Thu, Sep 26, 8:56 PM
Unknown Object (File)
Sep 3 2024, 11:11 AM
Unknown Object (File)
Aug 27 2024, 12:35 PM
Unknown Object (File)
Aug 27 2024, 10:08 AM
Unknown Object (File)
Aug 27 2024, 8:51 AM
Unknown Object (File)
Aug 27 2024, 7:06 AM
Unknown Object (File)
Aug 27 2024, 12:39 AM
Subscribers
None

Details

Summary

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

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable