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
F14020437: D18976.id45523.diff
Wed, Nov 6, 12:34 AM
F14010256: D18976.id45523.diff
Thu, Oct 31, 6:44 AM
F14007695: D18976.id.diff
Tue, Oct 29, 10:07 AM
F14007346: D18976.diff
Tue, Oct 29, 4:12 AM
F13968242: D18976.id45510.diff
Wed, Oct 16, 7:33 PM
Unknown Object (File)
Oct 11 2024, 4:24 AM
Unknown Object (File)
Sep 26 2024, 4:33 PM
Unknown Object (File)
Sep 23 2024, 3:28 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