Proposal: Humanizing unread message logic for Chat API

Zeyad_Zahran

New member
Hello everyone! 👋

I’m Zeyad, and I’ve previously contributed to the talawa-admin project with a merged PR: talawa-admin #7172. I'd love to hear your feedback

I’m currently exploring the talawa-api repository as I prepare for GSoC 26 , and I found an interesting TODO in the integration tests at:
/home/talawa/api/test/graphql/types/Chat/Chat.test.ts

I have opened an issue to address the humanized unread message logic here: talawa-api #5248

I’d love to hear your thoughts on the proposed approach (auto-updating `lastReadAt` upon message creation) or if there’s a preferred way to handle this in the API before I start working on the PR.

Thanks!
 
Last edited:
Back
Top