fix: align UserQuotaSnapshot type with getUserLimitUsage return type

[github-actions]

CI Auto-Fix for PR #507

Original PR: #507
Failed CI Run: PR Build Check

Problem

The CI failed with a TypeScript type mismatch error in src/app/[locale]/dashboard/quotas/users/page.tsx:75:

Type '{ rpm: { current: number; limit: number | null; window: "per_minute"; }; dailyCost: { current: number; limit: number | null; resetAt: Date; }; } | null' is not assignable to type 'UserQuotaSnapshot | null'.

Root Cause

The getUserLimitUsage action returns quota data with:

• rpm.limit: number | null
• dailyCost.limit: number | null
• dailyCost.resetAt: Date (required)

But the UserQuotaSnapshot interface expected:

• rpm.limit: number (not nullable)
• dailyCost.limit: number (not nullable)
• dailyCost.resetAt?: Date (optional)

Fix Applied

File	Change	Type
src/app/[locale]/dashboard/quotas/users/_components/types.ts	Updated UserQuotaSnapshot interface to match actual data structure	Type definition alignment

Changes made:

• rpm.limit: number → rpm.limit: number \| null
• dailyCost.limit: number → dailyCost.limit: number \| null
• dailyCost.resetAt?: Date → dailyCost.resetAt: Date

Verification

✅ bun run typecheck passes
✅ bun run lint passes
✅ No logic changes made
✅ Minimal, targeted type fix only

---

Auto-generated by Claude AI

Greptile Summary

Fixes TypeScript type mismatch between UserQuotaSnapshot interface and getUserLimitUsage action return type. The action returns quota limits as nullable (number | null) and resetAt as required, but the interface expected non-nullable limits and optional resetAt.

Changes:

• rpm.limit: number → number | null
• dailyCost.limit: number → number | null
• dailyCost.resetAt: Date? → Date (now required)

This aligns the type definition with the actual runtime data structure returned by getUserLimitUsage() in src/actions/users.ts:1233-1295, which retrieves user quota data where limits can be null (unlimited) and resetAt is always present from getDailyResetTime().

Confidence Score: 5/5

• This PR is safe to merge with no risk - it's a pure type definition fix with no runtime logic changes
• Score of 5 reflects that this is a straightforward type alignment fix that corrects a TypeScript compilation error. The changes are minimal (3 field type adjustments), accurately reflect the actual runtime data structure, and have been validated by passing typecheck and lint. No logic changes were made, only type definitions updated to match reality.
• No files require special attention

Important Files Changed

Filename	Overview
src/app/[locale]/dashboard/quotas/users/_components/types.ts	Aligned UserQuotaSnapshot type with getUserLimitUsage return type - made limits nullable and resetAt required

Sequence Diagram

sequenceDiagram
    participant Page as UsersQuotaPage
    participant Action as getUserLimitUsage
    participant DB as Database
    participant Type as UserQuotaSnapshot
    
    Page->>Action: getUserLimitUsage(userId)
    Action->>DB: findUserById(userId)
    DB-->>Action: User data
    Action->>DB: sumUserCostToday(userId)
    DB-->>Action: dailyCost (number)
    Action->>Action: Build response with<br/>limit: number | null<br/>resetAt: Date
    Action-->>Page: { rpm, dailyCost }
    Page->>Type: Assign to quota: UserQuotaSnapshot
    Note over Page,Type: ✅ Type alignment fixed:<br/>limits now nullable<br/>resetAt now required

Loading