Page MenuHomePhabricator

Accept `null` via `conduit.edit` to unassign a task
ClosedPublic

Authored by epriestley on Jan 31 2018, 7:14 PM.
Tags
None
Referenced Files
F19925389: D18976.id45523.diff
Tue, Apr 7, 10:25 AM
F19887191: D18976.diff
Mon, Mar 23, 12:11 AM
F19681989: D18976.id45523.diff
Feb 8 2026, 11:05 PM
F19619998: D18976.diff
Feb 4 2026, 11:26 AM
F18902613: D18976.diff
Nov 8 2025, 1:58 AM
F18851580: D18976.id45510.diff
Oct 31 2025, 2:19 AM
F18680426: D18976.id45510.diff
Sep 26 2025, 2:40 AM
F18594042: D18976.id.diff
Sep 12 2025, 4:48 PM
Subscribers
None

Details

Summary

See https://discourse.phabricator-community.org/t/maniphest-edit-to-unassign-owner-documentation-is-wrong/1053. This unusual field doesn't actually accept null, although the documentation says it does and that was the intent.

Accept null, and show phid|null in the docs.

Test Plan

Viewed docs, saw phid|null. Unassigned with null.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable