BoosAPI

Files

T

boos 7c9a1e2cc4 fix(rust): match main's drizzle-style camelCase response shape

Frontend reads main's drizzle-generated camelCase fields (siteId,
accessToken, oauthProvider, etc.) and a nested `site: {...}` on each
account row. Rust models were serializing snake_case with no nested
site, so PUT /api/sites/undefined/disabled-models 404s, account.site?.id
is undefined everywhere, and similar shape mismatches break Accounts,
Sites, Tokens, and Dashboard pages.

- Add #[serde(rename_all = "camelCase")] to every model struct in
  src/db/models/* (Account, AccountToken, Site, User, Event,
  TokenRoute, RouteChannel, BackgroundTask, DownstreamApiKey,
  Organization/Member/Invitation, SiteAnnouncement)
- list_accounts now nests `site: {...}` per row, matching main's
  `{...account, site: {...}}` shape from accountsOverviewService
- admin user-detail endpoint emits camelCase keys (totalRequests,
  totalCost, last7DaysCost, recentLogs, promptTokens, completionTokens,
  totalTokens, createdAt) to match the frontend
- routes refresh endpoint now emits both affected_routes and
  affectedRoutes for forward compat

Co-Authored-By: Kiro <noreply@kiro.dev>

2026-05-20 07:21:40 +08:00

account.rs

fix(rust): match main's drizzle-style camelCase response shape

2026-05-20 07:21:40 +08:00

background_task.rs

fix(rust): match main's drizzle-style camelCase response shape

2026-05-20 07:21:40 +08:00

downstream_api_key.rs

fix(rust): match main's drizzle-style camelCase response shape

2026-05-20 07:21:40 +08:00

event.rs

fix(rust): match main's drizzle-style camelCase response shape