upswyng
upswyng copied to clipboard
resources filter by sub-category
Problem
We currently use the sub-category endpoint to serve resources by category (example sub-category page). After we tackle #488, we'll be accessing lists of resources in the web project from two separate endpoints.
It'd be ideal to standardize how we access resources.
Solution
Ideally we'd like to have our current resources endpoint support filtering by sub-category. That way, we can use one endpoint for fetching resources.
API Updates
- add an optional
subcategories
query param to the resources endpoint that accepts a string equaling a comma-separated list of subcategories we wish to filter resources by, e.g./resources?subcategories=emergency,family
- update the useResourcesBySubcategory hook to consume resources using that updated endpoint
Tech Notes
- The current
/resources
endpoint currently supports filtering resources by a list of comma-separated IDs and possibly categories due to #488 if that is completed before. We'll need to make sure we also honor the current filtering byids
andcategories
that exists on this endpoint. This means that if we provide bothids
andcategories
andsubcategories
as filters, we only return resources that match the passed ids AND belong to one or more of the passed categories AND belong to one or more of the passed subcategories.