Skip to content

Document usage limits policy reset fields in OpenAPI spec#144

Merged
itsthusharashenoi merged 1 commit into
masterfrom
fix/usage-limits-list-periodic-reset
Jun 12, 2026
Merged

Document usage limits policy reset fields in OpenAPI spec#144
itsthusharashenoi merged 1 commit into
masterfrom
fix/usage-limits-list-periodic-reset

Conversation

@itsthusharashenoi

Copy link
Copy Markdown

Summary

Updates the OpenAPI spec to match what the usage limits list and get APIs already return.

Related backend fix: albus#2165 — list now returns the same policy fields as get by passing optional select in the list controller.

What changed

Added three missing fields to UsageLimitsPolicy in openapi.yaml:

  • periodic_reset_days
  • next_usage_reset_at
  • last_reset_at

List and get both use this schema, but these reset-related fields were returned by the API and not documented.

Note

These fields can be null for policies using periodic_reset: monthly or weekly. That is expected — they mainly apply to periodic_reset_days policies. List and get behave the same here.

Test plan

  • Check GET /policies/usage-limits docs show the three new fields on list items
  • Check GET /policies/usage-limits/{policyUsageLimitsId} docs show the same fields
  • Merge with albus#2165

Made with Cursor

Add periodic_reset_days, next_usage_reset_at, and last_reset_at to
UsageLimitsPolicy so list and get responses match the documented schema.

Co-authored-by: Cursor <cursoragent@cursor.com>
@itsthusharashenoi itsthusharashenoi merged commit a2191f4 into master Jun 12, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants