Skip to content

fix: channel can be undefined, don't force it #102

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 3 commits into from
Jul 26, 2023
Merged

fix: channel can be undefined, don't force it #102

merged 3 commits into from
Jul 26, 2023

Conversation

callaars
Copy link
Contributor

Description

Forcing a channel to exist when it clearly can be undefined is not good practice. We have had crashes due to channel being undefined.

CHANGELOG

  • [FIXED] Channel is an optional, make sure to check if it exists.

@fbenevides
Copy link
Contributor

Hey @callaars, thanks for the contribution.

Looking at CI workflow, there are a few places where we also need to change the returning value (PusherChannel)

This is the file: example/src/App.tsx. Could you please update that as well?

Thanks

@fbenevides fbenevides merged commit d7b40eb into pusher:master Jul 26, 2023
@ArendtKacper
Copy link

when will it be at npm?

@fbenevides
Copy link
Contributor

@ArendtKacper It's already available in the latest version

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.

3 participants