-
Notifications
You must be signed in to change notification settings - Fork 14
feat: make stabilization delay configurable #348
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: 11-10-fix_add_delay_after_establishing_the_realtime_channel_so_it_is_stable
Are you sure you want to change the base?
Conversation
|
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
106f9d3 to
0c591fe
Compare
76f307e to
48e0581
Compare
|
| Command | Status | Duration | Result |
|---|---|---|---|
nx affected -t lint typecheck test --parallel -... |
❌ Failed | 9m 2s | View ↗ |
☁️ Nx Cloud last updated this comment at 2025-11-11 16:41:02 UTC
48e0581 to
bc7239e
Compare
7d415e0 to
1da476a
Compare
5c7b1b4 to
771a319
Compare
| ) { | ||
| this.#supabase = supabase; | ||
| this.#reconnectionDelay = opts.reconnectDelayMs ?? 2000; | ||
| this.#stabilizationDelay = opts.stabilizationDelayMs ?? 300; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The nullish coalescing operator (??) treats 0 as a valid value, but since 0 is falsy in JavaScript, using || would cause issues. The current implementation with ?? is correct and will properly handle 0 as a valid delay value.
To verify this behavior:
const test1 = 0 ?? 300; // result: 0
const test2 = 0 || 300; // result: 300The test case for 0ms delay should pass with the current implementation.
Spotted by Graphite Agent
Is this helpful? React 👍 or 👎 to let us know.
1da476a to
81fcc5b
Compare
771a319 to
01e016c
Compare

No description provided.