Details
Details
Tested in combination with the rest of the stack:
- Make sure membership operations (user joining / leaving) don't appear in MessagePreview
- Make sure reactions to the viewer's messages still appear in MessagePreview
- Make sure reactions to other user's messages don't appear in MessagePreview
- Test fresh login to thread with only one message in the last 14 days, which is a reaction to a non-viewer message. Make sure the reaction initially appears in MessagePreview, but then is replaced after more messages are fetched by the client
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
lib/hooks/message-hooks.js | ||
---|---|---|
127 | I included this sleep here for two reasons:
|
Comment Actions
This approach sounds dangerous because it can potentially result in fetching a huge number of messages into memory. However, the scenario in which that could happen is almost impossible.