Skip to content
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

Fixed the issue in #114: Disposing an inactive WebsocketClient no longer triggers DisconnectionHappened #116

Merged
merged 1 commit into from
Oct 13, 2022

Conversation

JacquelineCasey
Copy link
Contributor

See #114.

I updated a test to catch this new behavior, and then I updated the code accordingly (this only required a tiny change).

- Updated a test to catch this issue
- Updated the WebsocketClient.cs accordingly
@Marfusios
Copy link
Owner

Hey @jackcasey067 ,
sorry for the late response.
Thanks for the PR.

Theoretically, it is a breaking change, because someone can expect IsRunning=false inside DisconnectionHappened stream.
But I believe it is minor.
Merging.

@Marfusios Marfusios merged commit 0fbe49e into Marfusios:master Oct 13, 2022
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.

2 participants