nextcloud / nextcloud/talk-android
Handle more signaling messages
Open
Nobody has claimed this yet.
1. to develop
enhancement
- Dominant language
- Kotlin
- Stars
- 739
- Forks
- 321
- Avg merge
- 14h 59m
- Merged PRs (30d)
- 151
Description
More signaling messages should be handled.
This could also reduce usage of requests by recursive calls (for example for getRoomInfo, see https://github.com/nextcloud/talk-android/pull/2815)
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 reviewing the signaling-message handling and the getRoomInfo request flow referenced in the issue, then compare the approach in pull request 2815. Identify which additional signaling messages are in scope and define done as handling them while reducing recursive requests; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- audio-video-rtc, mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100