The new design of MM involves serving data over an API. We need to design the API - how the requests/response pairs will be formatted, languages and frameworks used etc.
We know that we want to serve the following from the MM BE:
1) Search by search term and/or prop filters (search query parameters -> array of indexes)
N * category IDs + (optional) text fragment -> list of indexes
http://blah/api/search/categories=A,B,C/text=D
2) Search by search term and/or prop filters (search query parameters + fields to return -> paginated array of objects)
Track under CWM in clockify
Description
The new design of MM involves serving data over an API. We need to design the API - how the requests/response pairs will be formatted, languages and frameworks used etc.
We know that we want to serve the following from the MM BE: 1) Search by search term and/or prop filters (search query parameters -> array of indexes) N * category IDs + (optional) text fragment -> list of indexes http://blah/api/search/categories=A,B,C/text=D
2) Search by search term and/or prop filters (search query parameters + fields to return -> paginated array of objects)
3) Retrieve popup contents (index -> Html) http://blah/api/item/[index]
4) Retrieve full set of lng/lats ( _ -> JSON array)
Acceptance Criteria