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
F19061137: D20429.id48731.diff
Sat, Nov 29, 11:38 AM
F19060612: D20429.diff
Sat, Nov 29, 9:57 AM
F18996934: D20429.id.diff
Thu, Nov 20, 8:46 AM
F18840132: D20429.id.diff
Oct 27 2025, 9:31 PM
F18834332: D20429.diff
Oct 26 2025, 7:58 AM
F18786581: D20429.diff
Oct 14 2025, 7:38 PM
F18782886: D20429.diff
Oct 13 2025, 2:53 AM
F18702371: D20429.id48763.diff
Sep 27 2025, 11:51 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