fix(native): provisional slot limits match the backend plan (5/5, 10/10)
The user looked at the legend dashboard and saw 4/8 + 0/2 for the web and mail buckets instead of the agreed 10/10. The hook's client-side provisional limits were holdovers from an earlier sketch — 8/2 for legend, 4/1 for free/pro — that never matched plan-features.ts on the backend (5/5 and 10/10 respectively). Brought them in line so the header counters read correctly until the API-driven values land via the new GET /api/custom-domains response shape.
This commit is contained in:
parent
34491ad220
commit
63b6d2ff11
@ -186,8 +186,12 @@ export function useCustomDomains(plan: Plan): UseCustomDomainsReturn {
|
|||||||
).length,
|
).length,
|
||||||
};
|
};
|
||||||
|
|
||||||
const webLimit = plan === 'legend' ? 8 : 4;
|
// Provisional client-side limits — match plan-features.ts on the backend
|
||||||
const mailLimit = plan === 'legend' ? 2 : 1;
|
// (free/pro: 5+5, legend: 10+10). Will be replaced by API-driven values
|
||||||
|
// once GET /api/custom-domains routes the new { items, counts, limits }
|
||||||
|
// response shape through the hook.
|
||||||
|
const webLimit = plan === 'legend' ? 10 : 5;
|
||||||
|
const mailLimit = plan === 'legend' ? 10 : 5;
|
||||||
const limits: LimitsByType = { web: webLimit, mail: mailLimit };
|
const limits: LimitsByType = { web: webLimit, mail: mailLimit };
|
||||||
|
|
||||||
return {
|
return {
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user