feat(billing): add demo equivalences config for the nav compute gauge#3899
Conversation
Ships a neutral devkit demo billing.equivalences block so the Vue nav compute-gauge renders its capacity-chip estimate out of the box and the serverConfig.billing.equivalences contract is documented in config. The auth config endpoint already serves this key verbatim; downstream projects override with their own kinds/labels/unit costs (or omit it -> gauge shows raw units). Supports pierreb-devkit/Vue#4349.
|
Warning Review limit reached
More reviews will be available in 46 minutes and 49 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
Adds a devkit-default billing.equivalences configuration (and inline documentation) so the Vue nav compute gauge can render capacity equivalence estimates out-of-the-box via serverConfig.billing.equivalences.
Changes:
- Add demo
billing.equivalencesentries (easy/hard) with example unit costs and labels. - Document the expected shape/behavior of
serverConfig.billing.equivalencesin the billing module config.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #3899 +/- ##
=======================================
Coverage 92.66% 92.66%
=======================================
Files 169 169
Lines 5535 5535
Branches 1778 1777 -1
=======================================
Hits 5129 5129
Misses 326 326
Partials 80 80
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
…ault Correct the comment: the block ships as the billing base config, so omitting it downstream inherits the demo values — disable explicitly with [] / null. Drop the '~' from the example to match the exact integer counts the gauge renders.
What
Ship a neutral devkit demo
billing.equivalencesconfig so the Vue nav compute-gauge renders its capacity-chip estimate out of the box, and theserverConfig.billing.equivalencescontract is documented in config.How
billing.equivalencesarray (easy operations/heavy operations) to the billing module config.modules/auth/controllers/auth.controller.jsalready servesconfig.billing?.equivalences ?? nullverbatim to the client.{ kind:'easy'|'hard', unitCost:number>0, label:string }.Supports pierreb-devkit/Vue#4349.