Skip to content

[2/n] Add cynic types for tiered usage visibility#11110

Merged
IsaiahWitzke merged 1 commit into
iw/seat-caps-changes-2from
iw/usage-visibility-cynic-types
May 16, 2026
Merged

[2/n] Add cynic types for tiered usage visibility#11110
IsaiahWitzke merged 1 commit into
iw/seat-caps-changes-2from
iw/usage-visibility-cynic-types

Conversation

@IsaiahWitzke
Copy link
Copy Markdown
Contributor

Adds cynic types for tiered usage visibility + billing-cycle usage history to crates/graphql/src/api/billing.rs. Inert until a follow-up PR queries them.

Stacked on #11109.

Conversation: https://staging.warp.dev/conversation/cc554fe4-8a54-4573-a4c7-c3c9615ac225
Plan: https://staging.warp.dev/drive/notebook/yoCVtAF3BCHp5sjKSxraIu

Co-Authored-By: Oz oz-agent@warp.dev

@cla-bot cla-bot Bot added the cla-signed label May 16, 2026
Adds the Rust shapes for the new server-side surface from the
tiered-usage-visibility spec, all in crates/graphql/src/api/billing.rs:

- UsageVisibilityPolicy and UsageVisibilityGranularity, with the new
  field plumbed through the Tier fragment.
- BillingCycleUsageHistory, BillingCycleUsageSummary, UsageEntry.
- AICreditsUsageAndCostSubjectType, AICreditsUsageAndCostType (with
  AGGREGATE sentinel), AICreditsUsageBucket (with AGGREGATE), and
  AICreditsUsageSource (with AGGREGATE).

All new enums carry a #[cynic(fallback)] Other(String) variant so the
client stays forward-compatible with future server-side additions.
Nothing in the client queries these fields yet; that comes in
subsequent PRs.

Co-Authored-By: Oz <oz-agent@warp.dev>
@IsaiahWitzke IsaiahWitzke force-pushed the iw/usage-visibility-cynic-types branch from cfd83e0 to bada5ca Compare May 16, 2026 18:41
@IsaiahWitzke IsaiahWitzke merged commit bada5ca into iw/seat-caps-changes-2 May 16, 2026
3 checks passed
@IsaiahWitzke IsaiahWitzke deleted the iw/usage-visibility-cynic-types branch May 16, 2026 19:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant