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

Feature/rea 1808 use separate channel object #1655

Conversation

mschristensen
Copy link
Contributor

Depends on #1651

@github-actions github-actions bot temporarily deployed to staging/pull/1655/features February 29, 2024 17:43 Inactive
@github-actions github-actions bot temporarily deployed to staging/pull/1655/typedoc February 29, 2024 17:44 Inactive
@github-actions github-actions bot temporarily deployed to staging/pull/1655/bundle-report February 29, 2024 17:44 Inactive
Copy link
Contributor

@VeskeR VeskeR left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, some minor test comments, but they are not blockers really

test/realtime/channelgroup.test.js Outdated Show resolved Hide resolved
test/realtime/channelgroup.test.js Outdated Show resolved Hide resolved
The Channels object used by the ChannelGroup for internal channel
operations no longer shares the same object exposed on the client via
the .channels() method. This is to ensure that independent usage of an
individual channel that happens to be included in a channel group is not
impacted by its usage in the channel group.
Now that we can correctly handle a channel group and channel being used
independently from the same client, this tidies up the leave test to
remove the additional client previously needed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants