Neighborhood filtering was UUID-only; add name-based search on both GET /api/v1/cities/ and GET /api/v1/neighborhoods/ (the latter also matching by city name), and document all params for drf-spectacular. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
1.1 KiB
1.1 KiB
Changelog
[Unreleased]
Fixed
GET /api/v1/stores/— documented thecategory,neighborhood,search,lat, andlngquery params for drf-spectacular so they render in swagger. The filtering itself already worked; only the OpenAPI schema was missing them (apps/stores/views.py).GET /api/v1/products/— same issue: documented the existingstore,category, andsearchquery params for swagger (apps/catalog/views.py).
Added
GET /api/v1/cities/?search=— search cities by name (apps/locations/views.py); previously no text search existed.GET /api/v1/neighborhoods/?search=— search neighborhoods by neighborhood name or city name, alongside the existingcityUUID filter (apps/locations/views.py).- Test coverage for
StoreViewSetlist filtering (apps/stores/tests/test_store_list.py) — previously untested. - Test coverage for
ProductViewSetlist filtering (apps/catalog/tests/test_product_list.py) — previously untested. - Test coverage for
CityViewSet/NeighborhoodViewSetlist filtering (apps/locations/tests/test_location_list.py) — previously untested.