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
F15467799: D17443.id41955.diff
Thu, Apr 3, 6:04 PM
F15466804: D17443.id41940.diff
Thu, Apr 3, 9:58 AM
F15465374: D17443.id.diff
Wed, Apr 2, 5:58 PM
F15462727: D17443.diff
Tue, Apr 1, 5:11 PM
F15455407: D17443.diff
Sun, Mar 30, 12:11 AM
F15433521: D17443.diff
Mon, Mar 24, 11:38 PM
F15423190: D17443.id.diff
Mar 22 2025, 1:49 PM
F15386601: D17443.id41940.diff
Mar 15 2025, 12:56 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