docs: fix funding history limit — spec said 1000, code caps at 500#158
docs: fix funding history limit — spec said 1000, code caps at 500#1580x-SquidSol wants to merge 1 commit intodcccrypto:mainfrom
Conversation
The /funding/{slab}/history endpoint caps results at 500 rows
(funding.ts:346, PERC-8178) but the OpenAPI spec documented max 1000.
Clients requesting limit=800 would silently receive at most 500 results.
Aligns the spec with the actual implementation.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 3 minutes and 24 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ✨ 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 |
1 participant
Summary
/funding/{slab}/historycaps results at 500 rows (funding.ts:346, PERC-8178), but the OpenAPI spec documentedmaximum: 1000. Clients requesting?limit=800would silently receive at most 500 results.maximumfrom 1000 to 500 and description to match.Test plan
vitest runpasses (186/186 tests)MAX_ROWS = 500infunding.ts:346🤖 Generated with Claude Code