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
Unknown Object (File)
Thu, Nov 14, 4:07 AM
Unknown Object (File)
Tue, Nov 12, 6:52 AM
Unknown Object (File)
Tue, Nov 12, 6:51 AM
Unknown Object (File)
Sun, Nov 10, 7:44 AM
Unknown Object (File)
Wed, Nov 6, 12:34 AM
Unknown Object (File)
Thu, Oct 31, 6:44 AM
Unknown Object (File)
Tue, Oct 29, 10:07 AM
Unknown Object (File)
Tue, Oct 29, 4:12 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