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
F18566533: D18976.id.diff
Tue, Sep 9, 2:42 PM
F18502034: D18976.diff
Thu, Sep 4, 10:08 PM
F18106872: D18976.id45523.diff
Aug 10 2025, 11:29 PM
F18101953: D18976.id.diff
Aug 9 2025, 4:59 PM
F18099466: D18976.id45510.diff
Aug 9 2025, 5:12 AM
F18099222: D18976.id.diff
Aug 9 2025, 2:51 AM
F18099043: D18976.diff
Aug 9 2025, 12:54 AM
F18091990: D18976.id45510.diff
Aug 7 2025, 3:34 AM
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