KamoCRM

Rewrite billingApi client onto Account-based endpoints

Refactorkamo-internal
Ya
27 Aprili 2026, 22:36 UTC
Mwandishi
kamo
Ahadi ya
e911335

billingApi now talks to **************** instead of the old /groups/{groupId} routes. Top-level types renamed: - BillingGroup -> AccountBilling - BillingGroupMember -> AccountBillingMember - BillingGroupSubscription -> AccountSubscription - BillingGroupLicense -> AccountLicense - PlatformOrgGroupSummary -> PlatformAccountSummary - billingApi.groups.* -> billingApi.accounts.* - paymentMethods.setDefault -> paymentMethods.setPrimary - paymentMethods.attach now takes optional setPrimary flag Updated consumers: - PaymentMethodForm: prop renamed billingGroupId -> accountUid - PlansBillingTab: full migration to accounts API; group.id -> group.accountUid; group.title -> group.displayName; isDefault concept dropped - OrganizationsTab: PlatformOrgGroupSummary -> PlatformAccountSummary; org.groups -> org.accounts; row fields adapted - useEntitlements: **************** -> accountUid/DisplayName Legacy `@ts-nocheck`-flagged settings managers (StatsManager, FeaturesManager, BranchSetupManager) are kept compiling via deprecated stubs that return null/empty values — they need their own follow-up rework onto the new API.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila kitu kinaingia kwenye tovuti yako mwenyewe. Anza kwenye mpango wa bure na usome ukurasa huu tena katika mwezi mmoja.

Kuwa Huru MileleMtazamo wa bei