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
F13817740: D18976.id45523.diff
Fri, Sep 20, 2:44 AM
F13817555: D18976.diff
Fri, Sep 20, 12:55 AM
Unknown Object (File)
Wed, Sep 18, 1:05 AM
Unknown Object (File)
Wed, Sep 4, 9:13 AM
Unknown Object (File)
Mon, Aug 26, 12:37 AM
Unknown Object (File)
Sun, Aug 25, 8:02 PM
Unknown Object (File)
Aug 17 2024, 1:39 AM
Unknown Object (File)
Aug 6 2024, 10:07 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
Branch
null1
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 19299
Build 26080: Run Core Tests
Build 26079: arc lint + arc unit