-
Notifications
You must be signed in to change notification settings - Fork 25
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.
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
DMs: frontend state management rewrite #2996
Conversation
LAND-1136 DMs: rewrite FE state mgmt
Front-end state management for DMs/MultiDMs is still janky. We’re still using our older zustand store method for state management. This was done to avoid some extra work, but it’s causing some issues with rendering updates when messages receive new replies. It’s also not ideal to use an entirely different paradigm for this one part of the app. We should rewrite the frontend to use react-query for DMs/MultiDMs. This is probably two or three days worth of grinding. |
a684c18
to
f23df2a
Compare
…to useChatState, and remove commented out useChatState references
…d of unused hooks
…ame trackedPosts to trackedWrits in several places, use trackedPokes for dm reply deletes, listen for/updated trackedWrits for delivered status
…ccessible after clicking join
LAND-1222 dms: paging is broken
Retrieving writs relies on scries returning older/newer cursors for fetching the next batch of data in either direction. Right now they're broken and always return null. They should correctly return an ID for the next/previous message. |
Fixes LAND-1136
Fixes LAND-1222