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
F15441335: D18976.id.diff
Wed, Mar 26, 5:37 PM
F15426668: D18976.id45523.diff
Sun, Mar 23, 10:23 AM
F15381056: D18976.diff
Fri, Mar 14, 5:41 AM
Unknown Object (File)
Feb 17 2025, 12:12 AM
Unknown Object (File)
Feb 6 2025, 1:35 PM
Unknown Object (File)
Feb 5 2025, 1:53 AM
Unknown Object (File)
Jan 24 2025, 7:07 PM
Unknown Object (File)
Jan 18 2025, 8:01 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