Send echo=true connection param by default (RTC1a) - #2318
Tyagiquamar wants to merge 1 commit into
Conversation
Per spec RTC1a, the echoMessages option (default true) is sent as the echo query parameter on the WebSocket connection URL. Previously only echo=false was sent when explicitly disabled; the default sent no param.
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (3)
💤 Files with no reviewable changes (2)
Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 1 remain after this review. WalkthroughThe connection parameters now include ChangesEcho Parameter
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~8 minutes Change: Bug fix · Severity of issue fixed: Low Suggested reviewers: Merge Risk: ⚪ Minimal · up to Connections now explicitly carry the intended echo setting, and the default and opt-out WebSocket behaviors are asserted. No actionable merge-blocking risk remains in the reviewed change. Security Architecture ReviewSecurity architecture risk: ⚪ Minimal · up to The change makes an existing default explicit without changing the opt-out, authentication flow, or connection destinations. No introduced or worsened security risk was identified. Retained concerns Security review detailsSecurity Blast Radius
Trust Boundaries and Controls
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Warning Some tools did not complete. Review the errors below. 🔧 ESLint
ESLint install timed out. The project may have too many dependencies for the sandbox. 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. A rabbit checks the query string, Comment |
ttypic
left a comment
There was a problem hiding this comment.
LGTM, thanks for contribution
Per spec RTC1a, the echoMessages option (default true) is sent as the echo query parameter on the WebSocket connection URL. Previously only echo=false was sent when explicitly disabled; the default sent no param, relying on server-side default behavior.
Validation (node:20-bookworm container, matching CI 18.x/20.x matrix): RTC1a tests pass (2/2); pre-fix the default test fails with expected null to equal 'true'. Full realtime_client.test.ts (22 passing) and channel_subscribe.test.ts incl. RTL7f echo=false (22 passing). prettier/eslint clean on changed files.
Fixes #2206
Summary by CodeRabbit
Bug Fixes
echo=truewhen message echoing is enabled.Tests