CartItemView was registered on both /cart/items/ and
/cart/items/{item_uuid}/, so swagger listed POST/PATCH/DELETE on both
paths even though 3 of those 6 combinations raised a TypeError at
runtime (missing/unexpected item_uuid). Split into CartItemView (POST,
list path) and CartItemDetailView (PATCH/DELETE, detail path).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2.3 KiB
2.3 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).- Cart items:
CartItemViewwas registered on both/api/v1/cart/items/and/api/v1/cart/items/{item_uuid}/, so swagger showed POST/PATCH/DELETE on both paths — 3 of those 6 combinations crashed with aTypeErrorat runtime (item_uuidmissing or unexpected). Split intoCartItemView(POST only, list path) andCartItemDetailView(PATCH/DELETE only, detail path) so swagger only shows the combinations that actually work (apps/orders/views.py,apps/orders/urls.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).GET /api/v1/stores/now returnsphone_numberin the list (previously only on the single-store detail view) and adistance_kmfield, populated wheneverlat/lngare passed (apps/stores/serializers.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.
Changed
- Replaced hand-rolled
get_querysetfiltering withdjango-filterFilterSetclasses (apps/{stores,catalog,locations,reviews}/filters.py) andfilterset_fields(apps/ordersstatus).django-filterwas already installed and set asDEFAULT_FILTER_BACKENDSbut unused everywhere; params are now auto-documented in swagger by drf-spectacular's django-filter integration, so the manualOpenApiParameterdeclarations for those fields were removed (stores keepslat/lngmanual since geo-distance isn't a plain filter).