follow-up(LeftSidebar) - caching, broadcast optimizations
Open
Nobody has claimed this yet.
feature: conversations 👥
feature: frontend 🖌️
technical debt
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
Follow-ups:
- Don't cache conversations when nothing actually changed (we know it from the patching action)
- Add methods to post specific messages into the broadcast channel into the talkBroadcastChannel service as well as methods to add message handlers
- Think about centralized way to control what and when is synced, when to post messages
Originally posted by @ShGKme in https://github.com/nextcloud/spreed/issues/10203#issuecomment-1684264487
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 tracing the LeftSidebar patching action and the talkBroadcastChannel service to understand when conversations are cached and which broadcast messages are exchanged. Define the synchronization and handler changes with the maintainers, then verify that unchanged conversations are not cached and the required messages are delivered correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100