Some checks failed
Merchants can configure per-store product categories (e.g., Men,
Women, Accessories, Kids) that sellers select when entering loyalty
transactions. Enables per-category sales analytics.
Backend:
- New model: StoreTransactionCategory (store-scoped, max 10 per store)
- Migration loyalty_007: creates table + adds category_id FK on
loyalty_transactions
- New category_service.py with CRUD + validation
- New schemas/category.py (Create, Update, Response, ListResponse)
- Admin CRUD: GET/POST/PATCH/DELETE /admin/loyalty/stores/{id}/categories
- Store CRUD: GET/POST/PATCH/DELETE /store/loyalty/categories
- Stamp/Points request schemas accept optional category_id
- Stamp/Points services pass category_id to transaction creation
- TransactionResponse includes category_id + category_name
342 tests pass.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
43 lines
1.0 KiB
Python
43 lines
1.0 KiB
Python
# app/modules/loyalty/schemas/category.py
|
|
"""Pydantic schemas for transaction categories."""
|
|
|
|
from datetime import datetime
|
|
|
|
from pydantic import BaseModel, ConfigDict, Field
|
|
|
|
|
|
class CategoryCreate(BaseModel):
|
|
"""Schema for creating a transaction category."""
|
|
|
|
name: str = Field(..., min_length=1, max_length=100)
|
|
display_order: int = Field(default=0, ge=0)
|
|
|
|
|
|
class CategoryUpdate(BaseModel):
|
|
"""Schema for updating a transaction category."""
|
|
|
|
name: str | None = Field(None, min_length=1, max_length=100)
|
|
display_order: int | None = Field(None, ge=0)
|
|
is_active: bool | None = None
|
|
|
|
|
|
class CategoryResponse(BaseModel):
|
|
"""Schema for transaction category response."""
|
|
|
|
model_config = ConfigDict(from_attributes=True)
|
|
|
|
id: int
|
|
store_id: int
|
|
name: str
|
|
display_order: int
|
|
is_active: bool
|
|
created_at: datetime
|
|
updated_at: datetime
|
|
|
|
|
|
class CategoryListResponse(BaseModel):
|
|
"""Schema for listing categories."""
|
|
|
|
categories: list[CategoryResponse]
|
|
total: int
|