matrix-org / matrix-org/matrix-rust-sdk
[meta] Latest Event API, for Threads
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.3k
- Forks
- 500
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 106
Description
Theseus and Ariadne (Angelika Koffmann)
Extracted from https://github.com/matrix-org/matrix-rust-sdk/issues/4112 to reduce its scope.
The goal is to add Thread support in the LatestEvents API.
Plan
Note: Thread's events aren't persisted in the Event Cache yet. Until it's done, Latest Events for Threads are likely to be LatestEventValue::None, but we are still implementing that, so it's thread-aware™️ thread-ready™️.
- From the Event Cache:
- Add
RoomEventCacheGenericUpdatesupport for threads + thread pagination - Add
ThreadEventCache::rfind_map_event_in_memory_by - Add
RoomEventCache::threadto get aThreadEventCache - Update
LatestEventValueBuilder::new_remote_with_power_levelsto take into accountSelf::thread_id.
- Add
- From the Send Queue:
- Nothing in particular, just extract the thread root from
Thread::event_idto see if it matches the targeted thread.
- Nothing in particular, just extract the thread root from
- See if it closes https://github.com/matrix-org/matrix-rust-sdk/issues/5702.
- See where to store the
LatestEventValue, probably inThreadInfoorThreadSummary:
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 with the Event Cache items in the plan, especially RoomEventCacheGenericUpdate, ThreadEventCache::rfind_map_event_in_memory_by, and LatestEventValueBuilder::new_remote_with_power_levels, then review the Send Queue note about Thread::event_id. Done means LatestEvents is thread-aware, the listed cache and pagination work is covered, and the LatestEventValue storage location is settled in ThreadInfo or ThreadSummary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100