Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (5)
Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthroughThe SDK adds a reusable callable wrapper for ChangesCallable Open Panel
Priority: ➖ Normal Estimated code review effort: 3 (Moderate) | ~20 minutes Change: Bug fix · Severity of issue fixed: Medium Merge Risk: ⚪ Minimal · up to The SDK’s callable API behavior is covered for direct, property, and transpiled Function-helper invocation paths, with no actionable merge-blocking issue identified. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ 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 |
Fixes #240
Summary
Next.js 15.5 with Turbopack transforms optional calls such as:
window.op?.('track', ...)
into a call through
window.op.call(...).The callable
window.opProxy only resolved properties from the OpenPanelinstance, so native Function properties such as
.callreturnedundefined.This change:
.call,.apply,.bind, and other native Function behavior.Verification
Reproduced before the fix using the provided Next.js 15.5.7 Turbopack app:
Error: _window_op.call is not a functionAfter the fix, the same browser interaction completes without the error.
Also verified:
Summary by CodeRabbit
New Features
.call, are supported when invoking SDK operations.Bug Fixes