WebRTC and signaling are managing another list of participants
Open
Nobody has claimed this yet.
bug
feature: signaling 📶
feature: WebRTC 🚡
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 17h 55m
- Merged PRs (30d)
- 350
Description
Not really sure what they are about and why this is done.
But there is a peers list for call participants (needs a store?) and the conversation participant list (already has a vue store).
The custom array "collection" and the "models" should be transformed to decent JS instead of being stripped backbone things
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
Start by comparing the peers list used for call participants with the conversation participant list and its Vue store. Then inspect the custom array "collection" and the "models" mentioned in the issue; done means these Backbone-like structures have been transformed into standard JavaScript with participant state handled consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- audio-video-rtc, frontend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100