Skip to content

Expose reconnect mode #642

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

Merged
merged 1 commit into from
Mar 25, 2025
Merged

Expose reconnect mode #642

merged 1 commit into from
Mar 25, 2025

Conversation

pblazej
Copy link
Contributor

@pblazej pblazej commented Mar 21, 2025

The solution is a bit awkward, as connectionState does not cover .quick, but probably the only non-breaking one.

Resolves #368

@pblazej pblazej requested review from hiroshihorie and bcherry March 21, 2025 13:20
@pblazej
Copy link
Contributor Author

pblazej commented Mar 24, 2025

@bcherry This is just a proposal to unblock the issue, IMO the comments re "wrong" API are valid here.

@pblazej pblazej force-pushed the blaze/reconnection-state branch from d776290 to ca1d17b Compare March 25, 2025 11:57
@pblazej pblazej merged commit 299293a into main Mar 25, 2025
20 checks passed
@pblazej pblazej deleted the blaze/reconnection-state branch March 25, 2025 13:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Reconnecting State not activated while quick reconnects
2 participants