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
F15539278: D18976.id45510.diff
Fri, Apr 25, 12:24 AM
F15532534: D18976.id.diff
Wed, Apr 23, 4:09 PM
F15529747: D18976.diff
Tue, Apr 22, 10:12 PM
F15478110: D18976.id45523.diff
Mon, Apr 7, 8:36 PM
F15477930: D18976.id45510.diff
Mon, Apr 7, 6:50 PM
F15441335: D18976.id.diff
Mar 26 2025, 5:37 PM
F15426668: D18976.id45523.diff
Mar 23 2025, 10:23 AM
F15381056: D18976.diff
Mar 14 2025, 5:41 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