refactor: cache platform SDK connections per network#24
Conversation
connectPlatformSdk now returns a singleton per network instead of creating a fresh instance on every call. Added disconnectPlatformSdk() for callers to force a fresh connection. withConnectedPlatformSdk invalidates the cache on connection-level errors but keeps it alive for application errors.
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ 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 |
Summary
connectPlatformSdknow returns a cached singleton per network instead of creating a fresh EvoSDK instance on every call, eliminating repeated connection overhead for sequential operations.disconnectPlatformSdk(network)export so callers can force a fresh connection on error.withConnectedPlatformSdkinvalidates the cache on connection-level errors (transport/network failures) but keeps it alive for application-level errors (identity not found, etc.).Test plan
npm run buildpasses (verified locally)🤖 Generated with Claude Code