Page MenuHomePhabricator

When an invalid "constraints" parameter is provided to a "*.search" method, raise a more tailored error
ClosedPublic

Authored by epriestley on Apr 15 2019, 6:50 PM.
Tags
None
Referenced Files
F13196609: D20429.diff
Sun, May 12, 11:24 PM
F13173283: D20429.diff
Tue, May 7, 7:04 PM
Unknown Object (File)
Fri, May 3, 5:36 AM
Unknown Object (File)
Thu, Apr 25, 12:56 AM
Unknown Object (File)
Sat, Apr 20, 11:53 AM
Unknown Object (File)
Fri, Apr 19, 4:50 AM
Unknown Object (File)
Thu, Apr 18, 9:42 AM
Unknown Object (File)
Wed, Apr 17, 8:57 PM
Subscribers
None

Details

Summary

See https://discourse.phabricator-community.org/t/constraints-parameter-type-handling-in-maniphest-search/2636.

(The caller provided constraints={...} via cURL, but you can't mix JSON and HTTP parameters like that.)

Test Plan

Called curl 'http://local.phacility.com/api/maniphest.search?api.token=...&constraints=X' (with a valid API token), got a more sensible error.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable