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
F15408937: D20429.id.diff
Wed, Mar 19, 2:16 AM
F15294611: D20429.id48763.diff
Wed, Mar 5, 10:11 AM
Unknown Object (File)
Mon, Feb 24, 2:35 AM
Unknown Object (File)
Feb 15 2025, 2:39 AM
Unknown Object (File)
Feb 15 2025, 2:39 AM
Unknown Object (File)
Feb 15 2025, 2:39 AM
Unknown Object (File)
Feb 9 2025, 7:39 AM
Unknown Object (File)
Feb 9 2025, 7:39 AM
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