Skip to content

model: Investigate alternatives of passing messages to RecentSenders #824

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
sm-sayedi opened this issue Jul 18, 2024 · 0 comments
Open

model: Investigate alternatives of passing messages to RecentSenders #824

sm-sayedi opened this issue Jul 18, 2024 · 0 comments
Labels
a-model Implementing our data model (PerAccountStore, etc.)
Milestone
M6: Post-launch

Comments

@sm-sayedi
Copy link
Collaborator

This is a follow-up to #692.

Quoting Greg from #692 comment:

Ideally we'd have MessageStore.reconcileMessages handle passing the messages on to RecentSenders. That way as we add more and more data structures that similarly want to know about fetched messages, there's just one place we have to wire them in.

Now that we have a central message store (#648), we may want the RecentSenders data structure to receive its data (messages) from MessageStore.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
a-model Implementing our data model (PerAccountStore, etc.)
Projects
Flutter app
Status: No status
Milestone
M6: Post-launch
Development

No branches or pull requests
2 participants
@gnprice @sm-sayedi