alti3 Dataclasses
Execution Workflow
- Define dataclasses for transport boundaries with explicit field types.
- Use defaults and optionality intentionally to avoid ambiguous schemas.
- Combine with DTO configuration when write/read shapes diverge.
- Keep domain entities and transport dataclasses separate when needed.
Implementation Rules
- Favor immutable or clearly controlled mutation patterns.
- Avoid embedding persistence/session behavior in dataclasses.
- Keep field names/schema stable for clients.
- Validate nested dataclass behavior in serialization paths.
Example Pattern
from dataclasses import dataclass
from litestar import post
@dataclass
class CreateUser:
name: str
email: str
@post("/users")
async def create_user(data: CreateUser) -> dict[str, str]:
return {"email": data.email}
Validation Checklist
- Confirm request binding maps correctly into dataclass fields.
- Confirm response serialization matches expected JSON schema.
- Confirm DTO include/exclude behavior remains predictable.
Cross-Skill Handoffs
- Use
litestar-dtofor advanced shaping and nested field policy. - Use
litestar-pluginswhen switching to different model ecosystems.