Skip to content

feat(shared): credit dimensions and multipliers on rate-card rows - #3216

Draft
charlietlamb wants to merge 2 commits into
devfrom
charlie/dim-model
Draft

feat(shared): credit dimensions and multipliers on rate-card rows#3216
charlietlamb wants to merge 2 commits into
devfrom
charlie/dim-model

Conversation

@charlietlamb

@charlietlamb charlietlamb commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

A rate-card row can now carry named dimensions (property match → its own
flat or graduated rate, with optional priority) and multipliers (property
match → factor and/or add). Dimension names become usage-attribution keys
via buildUsageAttributionKey / parseUsageAttributionKey, so they are
bounded and cannot contain the separator.


Stack created with GitHub Stacks CLIGive Feedback 💬


Summary by cubic

Rate-card rows can now carry named dimensions and multipliers alongside their own flat or graduated rate, enabling property-based rates and adjustments without changing plain rows.

  • Dimensions support flat or graduated rates with optional priority; multipliers apply a factor and/or additive adjustment.
  • Match values normalize to strings, and dimension names are capped at 64 characters and cannot contain :: so they can be used in attribution keys.
  • Adds buildUsageAttributionKey and parseUsageAttributionKey for dimensioned attribution keys, and exports the match and dimension-name schemas.

Written for commit e3b0fa4. Summary will update on new commits.

Review in cubic

@vercel

vercel Bot commented Sep 2, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments
Project Deployment Actions Updated
checkout Ignored Ignored Sep 3, 2026 9:53am UTC
landing-page Ignored Ignored Sep 3, 2026 9:53am UTC

Request Review

A rate-card row can now carry named dimensions (property match → its own
flat or graduated rate, with optional priority) and multipliers (property
match → factor and/or add). Dimension names become usage-attribution keys
via buildUsageAttributionKey / parseUsageAttributionKey, so they are
bounded and cannot contain the separator.
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.

1 participant