Public API Routes — News & Senators

[calebyhan]

Motivation

News and Senators are the two most-visited public sections. Shipping these endpoints first allows the frontend team to integrate real data immediately and validates the full stack end-to-end (model → schema → route → response).

Deliverables

• Create a reusable pagination utility (app/utils/pagination.py) that accepts page and limit query params and returns offset/limit + total count metadata
• Implement GET /api/news — paginated, most recent first, only is_published=True
• Implement GET /api/news/:id — single article, 404 if not found or not published
• Implement GET /api/senators — filterable by search (name), district_id, committee (id), session (number); defaults to active senators in current session
• Implement GET /api/senators/:id — single senator with committee assignments included
• Create router files: app/routers/news.py, app/routers/senators.py
• Register routers in app/main.py
• Write integration tests using httpx.AsyncClient with a test database
• Seed test data in a pytest fixture

Important Notes

• Reference TDD Section 4.5.2
• Depends on SQLAlchemy Models — Core Entities (Admin, Senator, District, Leadership) #3 (Senator, District models), SQLAlchemy Models — Content Entities (News, Committee, Staff, Config) #4 (News models), Pydantic Schemas — Public Output DTOs #10 (output DTOs)
• Pagination response format: { items: [...], total: int, page: int, limit: int }
• Senator search should be case-insensitive partial match on first_name + last_name
• The committee filter on /api/senators should filter senators who are members of that committee (JOIN through CommitteeMembership)
• Do NOT implement admin routes yet