Repository navigation
chore(common): rename ServiceSavingsPlans -> ServiceSavingsPlansAll (closes #786) - #787
Conversation
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 36 seconds Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?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 reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. 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, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (27)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
|
@coderabbitai full review |
Rate Limit Exceeded
|
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
|
@coderabbitai review |
✅ Action performedReview finished.
|
3bf4670 to
e326233
Compare
|
@coderabbitai full review |
✅ Action performedFull review finished. |
e326233 to
7ffd4c0
Compare
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
@coderabbitai review |
✅ Action performedReview finished.
|
7ffd4c0 to
fe4ae55
Compare
|
@coderabbitai review |
✅ Action performedReview finished.
|
fe4ae55 to
e0442ed
Compare
…loses #786 Rename the umbrella sentinel ServiceSavingsPlans to ServiceSavingsPlansAll for clarity (distinguishing it from the per-plan-type slugs). Updates all callers across cmd/, internal/purchase/, pkg/common/, providers/aws/, and providers/azure/. Resolves conflict in service_details_codec.go by using ServiceSavingsPlansAll and combining comments from both sides.
077312a to
917af1e
Compare
|
Rebased onto origin/main, all CI checks passed, squash-merged. |
…loses #786 (#787) Rename the umbrella sentinel ServiceSavingsPlans to ServiceSavingsPlansAll for clarity (distinguishing it from the per-plan-type slugs). Updates all callers across cmd/, internal/purchase/, pkg/common/, providers/aws/, and providers/azure/. Resolves conflict in service_details_codec.go by using ServiceSavingsPlansAll and combining comments from both sides.
Summary
ServiceSavingsPlanswas an umbrella sentinel whose name looked identical to thefour per-plan-type slugs (
ServiceSavingsPlansCompute, etc.), making it unclearat call sites whether a variable held the umbrella or a specific plan type.
Changes
pkg/common/types.go-- rename constantServiceSavingsPlanstoServiceSavingsPlansAll; string value"savingsplans"is unchanged (DB columnlocked by issue Normalize 'savings-plans' vs 'savingsplans' identifier across frontend + backend cloud-commitments-platform#7). Updated docstring makes the sentinel/umbrella intent
explicit and references
SavingsPlansPlanTypes().pkg/common/types.go-- addSavingsPlansPlanTypes() []ServiceTypereturning the 4 per-plan-type slugs in canonical order
(Compute -> EC2Instance -> SageMaker -> Database). Unit test in
pkg/common/types_test.goasserts length 4, canonical order, and that everyreturned slug passes
IsSavingsPlan.pkg/common/types.go-- updateIsSavingsPlanswitch arm toServiceSavingsPlansAll; no behaviour change. Updated 23 other call-site files(providers, cmd, internal/purchase) with the same mechanical swap.
Verification
go build ./...cleango test .../pkg/common/... .../providers/aws/recommendations/... .../internal/api/... -count=1 -short: 1802 tests passgit grep -E '\bServiceSavingsPlans\b' -- '*.go': 0 hits (no stale bare references)git grep ServiceSavingsPlansAll -- '*.go': 82 occurrences (matches the pre-rename count of the bare identifier)Notes
PR #785 (closes #784, currently open and mid-CR) references
ServiceSavingsPlansinits diff. It will need a trivial rebase after this merges -- a mechanical
ServiceSavingsPlans->ServiceSavingsPlansAllidentifier swap on its branch, nologic change. No other in-flight branch references the bare identifier.
Closes #786
Refs LeanerCloud/cloud-commitments-platform#7 #785