[FOLLOW-UP] Additional message processing from chat-relay
Open
Nobody has claimed this yet.
feature: frontend 🖌️
feature: signaling 📶
- Dominant language
- JavaScript
- Stars
- 2.2k
- Forks
- 586
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
Missing from chat-relay:
- #16687
- Once per 2 minutes
- Fetch back from the last known? forward from the last given by server?
- #16406
- Check for guests, email guests, federated users
- API: https://github.com/nextcloud/spreed/pull/16886
Two bonuses to process:
- Poll sys messages now include additional information #16137
- Thread object is included in thread-created sys message
Originally posted by @DorraJaouad in https://github.com/nextcloud/spreed/pull/16406#discussion_r2556523148
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 linked follow-up context in #16406, the API change in PR #16886, and the remaining task in #16137. Trace how chat-relay processes poll and thread-created system messages; done means poll messages include the additional information and thread-created messages include the thread object.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100