Add REST API endpoints for games, runs, and encounters
Implement 13 endpoints: read-only reference data (games, routes, pokemon), run CRUD with cascading deletes, and encounter management. Uses Pydantic v2 with camelCase alias generation to match frontend types, and nested response schemas for detail views. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,30 @@
|
||||
from app.schemas.encounter import (
|
||||
EncounterCreate,
|
||||
EncounterDetailResponse,
|
||||
EncounterResponse,
|
||||
EncounterUpdate,
|
||||
)
|
||||
from app.schemas.game import GameDetailResponse, GameResponse, RouteResponse
|
||||
from app.schemas.pokemon import (
|
||||
PokemonResponse,
|
||||
RouteEncounterDetailResponse,
|
||||
RouteEncounterResponse,
|
||||
)
|
||||
from app.schemas.run import RunCreate, RunDetailResponse, RunResponse, RunUpdate
|
||||
|
||||
__all__ = [
|
||||
"EncounterCreate",
|
||||
"EncounterDetailResponse",
|
||||
"EncounterResponse",
|
||||
"EncounterUpdate",
|
||||
"GameDetailResponse",
|
||||
"GameResponse",
|
||||
"RouteResponse",
|
||||
"PokemonResponse",
|
||||
"RouteEncounterDetailResponse",
|
||||
"RouteEncounterResponse",
|
||||
"RunCreate",
|
||||
"RunDetailResponse",
|
||||
"RunResponse",
|
||||
"RunUpdate",
|
||||
]
|
||||
|
||||
Reference in New Issue
Block a user