Org Web Adapter

Editing hungryroot/jira/be_7471_create_serializers_viewsets_and_hook_up_url_routing_for_cookbooks.org

:PROPERTIES:
:ID:       a6802c80-e6ab-4340-80fc-50fd453ce01d
:END:
#+title: BE-7471 Create serializers, viewsets and hook up URL routing for Cookbooks

- source :: https://hungryroot.atlassian.net/browse/BE-7471
- tags   :: [[id:3a477c02-e26d-40f7-a719-0aa1cd169dd8][Hungryroot API Project]]
- epic   :: [[id:2f37c7bc-6cb2-47ae-a513-f634e5c4cfbb][EP-627 Exp 232: Cookbook MVP]]
- sprint :: [[id:c4663d81-db80-4eb0-a898-9f2c4aea9023][HR BE Sprint 107]]
- status :: [[id:ec92a960-cac1-4b05-b4f5-25a2935eea75][Status - To Do]]
- priority :: [[id:87c238a1-1c0d-4ee9-b8a5-6876cabb93b4][Priority - High]]
- points :: 2

* Description
We need to expose the cookbooks functionality via the REST API. This task
involves creating Django Rest Framework (DRF) serializers, ViewSets, and
configuring URL routing.

Crucially, the ViewSet logic must delegate write operations (create/update) to
the existing CookbookService to ensure the upsert behavior and transactional
integrity implemented in BE-7470 are enforced via the API.

This task also includes writing integration tests for the API endpoints to
ensure the serializers, views, and service layer interact correctly.

** Acceptance Criteria

*** Serializers:

- Create serializers for Cookbook, CookbookAuthor, CookbookSection, and CookbookItem.
- Implement nested serializers for writing (e.g., accepting items data within the Cookbook payload).
- Ensure validation logic matches model constraints.

*** ViewSets:

- Create a CookbookViewSet extending ModelViewSet or ViewSet.
- Override create and update methods to call CookbookService.upsert_cookbook instead of direct model serialization saving.
- Ensure read operations (list/retrieve) function as expected.

*** URL Routing:

- Register the CookbookViewSet with the default router.
- Ensure endpoints are accessible (e.g., /api/cookbooks/, /api/cookbooks/{slug}/).

*** API Testing:

- Write integration tests using APIClient.
- Test GET (list/retrieve) for correct data structure.
- Test PUT (upsert) to verify service layer invocation and transactional behavior.
- Test validation errors (e.g., missing required fields).

** Documentation:

Ensure API schema (Swagger/Redoc) reflects the new endpoints correctly.

** Technical Implementation Notes

*** Service Integration:

- Do not call serializer.save() directly for write operations.
- Nested Writes: Ensure the Serializer write methods handle the nested items and author data correctly before passing it to the Service.
- Permissions: Apply standard project permissions (e.g., IsAuthenticated or IsAdminUser) as per project standards.

*** Testing:

Use django.test.TestCase or pytest with APIClient.

Verify that a PUT request with nested items triggers the _update_items logic in
the service (upsert).