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
Unknown Object (File)
Thu, Jun 5, 4:19 PM
Unknown Object (File)
Mon, Jun 2, 12:59 PM
Unknown Object (File)
May 28 2025, 8:52 PM
Unknown Object (File)
May 27 2025, 10:41 AM
Unknown Object (File)
May 7 2025, 3:10 PM
Unknown Object (File)
May 7 2025, 3:10 PM
Unknown Object (File)
May 7 2025, 12:52 AM
Unknown Object (File)
Apr 26 2025, 11:33 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
Branch
constraints1
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 22601
Build 30967: Run Core Tests
Build 30966: arc lint + arc unit