-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
Fix the broken DM notification #2389
Fix the broken DM notification #2389
Conversation
isDMOrMention: isMentionedMe || getters.chatRoomAttributes.type === CHATROOM_TYPES.DIRECT_MESSAGE, | ||
isDMOrMention: isMentionedMe || targetChatroomState.attributes.type === CHATROOM_TYPES.DIRECT_MESSAGE, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was the cause of the issue.
getters.chatRoomAttributes
getter here is for a currently active chatroom which means the DM notification only works when the receivers of the DM have the chatroom open in their browsers and this is what I observed too.
Made a fix here where it checks if the target chatroom is DM or not, regardless of whether the chatroom is active or not.
group-income Run #3329
Run Properties:
|
Project |
group-income
|
Branch Review |
sebin/task/#2386-direct-message-notification-broken
|
Run status |
Passed #3329
|
Run duration | 09m 09s |
Commit |
7209a1178a ℹ️: Merge 4209910e57f218eee3b85b2042bcf7a54e70b2db into cd4e463201e39c77101340b487a8...
|
Committer | Sebin Song |
View all properties for this run ↗︎ |
Test results | |
---|---|
Failures |
0
|
Flaky |
0
|
Pending |
10
|
Skipped |
0
|
Passing |
111
|
View all changes introduced in this branch ↗︎ |
@taoeffect The PR is ready for review. I can work on updating(or creating) a test item to check for this bug separately from this PR later. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems to have done it!
resolve solution 1. of #2386
I can see the notification works properly now.