You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add support to craft data API requests where field names also support wildcards. Useful in "search" type usecases where multiple fields can be queried for the same data;
GET /data/contacts/address_*/*cambridge*
This would find the search term "cambridge" in any position, in any field that begins with address_ (i.e. address_line1, address_line2, address_city, etc).
A wildcard alone would also allow searching in any field:
GET /data/itineraries/*/Cambridge
The text was updated successfully, but these errors were encountered:
Open question on whether this should be allowed for POST modify queries as well. Potentially hairy with some database systems, and not exactly clear what the use case would be. On the other hand, it seems like a gotcha that it would work in one query method but not another.
Add support to craft data API requests where field names also support wildcards. Useful in "search" type usecases where multiple fields can be queried for the same data;
This would find the search term
"cambridge"
in any position, in any field that begins withaddress_
(i.e.address_line1
,address_line2
,address_city
, etc).A wildcard alone would also allow searching in any field:
The text was updated successfully, but these errors were encountered: