-
Notifications
You must be signed in to change notification settings - Fork 10.7k
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: Server sending 2 notifications when @all/@here
were used by a user without permissions
#32289
Conversation
🦋 Changeset detectedLatest commit: 351545f The changes in this PR will be included in the next version bump. This PR includes changesets to release 32 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #32289 +/- ##
===========================================
+ Coverage 55.48% 55.50% +0.02%
===========================================
Files 2371 2374 +3
Lines 52062 52095 +33
Branches 10651 10657 +6
===========================================
+ Hits 28888 28917 +29
- Misses 20636 20637 +1
- Partials 2538 2541 +3
Flags with carried forward coverage won't be shown. Click here to find out more. |
Looks like this PR is ready to merge! 🎉 |
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.
Can we add a brief description to the PR?
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.
Approving it on behalf of frontend team
https://rocketchat.atlassian.net/browse/SUP-549
Proposed changes (including videos or screenshots)
Issue(s)
Steps to test or reproduce
Further comments
A duplicate call to
api.broadcast
was causing that an error onBeforeSavePreventMention
was being propagated twice to clients.The global handler on
saveMessage
was updated to support using thedetails
property coming from meteor errors allowing the original hook to just throw and allow the caller to handle the error accordingly.