pusher / pusher/pusher-websocket-react-native
Support for user channels
Open
Nobody has claimed this yet.
feature-request
- Dominant language
- TypeScript
- Stars
- 76
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Description
No doubt on the roadmap but want to mention we've started our migration from pusher-js's RN module and have had to switch back from user channels to generic private channels. Would be great to have support for them in the new RN lib. Thanks.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the React Native library's existing private-channel support and the Pusher user-channel requirements before choosing an entry point. Done means the library supports user channels for the reported migration scenario and includes coverage demonstrating that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100