-
Notifications
You must be signed in to change notification settings - Fork 13k
fix: desktop notifications implementing privacy settings #36503
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: desktop notifications implementing privacy settings #36503
Conversation
🦋 Changeset detectedLatest commit: cd78879 The changes in this PR will be included in the next version bump. This PR includes changesets to release 37 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 |
|
Looks like this PR is ready to merge! 🎉 |
911e06f to
937fbd2
Compare
|
937fbd2 to
c054cb4
Compare
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## release-7.9.0 #36503 +/- ##
=================================================
- Coverage 65.70% 65.44% -0.26%
=================================================
Files 3174 3092 -82
Lines 105842 104283 -1559
Branches 20102 19720 -382
=================================================
- Hits 69539 68244 -1295
+ Misses 33624 33430 -194
+ Partials 2679 2609 -70
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
| window.focus(); | ||
|
|
||
| const jump = msgId && { jump: msgId }; | ||
| if (!notification.payload._id || !notification.payload.rid || !notification.payload.name) { |
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.
You removed _id and name from the destructing but still being in use here.
Also, rid is already destructured and you're accessing it from the full path.
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.
It is a revert of a previous PR. Since earlier case was also working fine I didnt change anything in the revert 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.
Done
| pattern: '/direct/:rid/:tab?/:context?', | ||
| params: { | ||
| rid, | ||
| rid: notification.payload.rid, |
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.
Why not use the destructured rid?
| pattern: '/live/:id/:tab?/:context?', | ||
| params: { | ||
| id: rid, | ||
| id: notification.payload.rid, |
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.
Same as before
ggazzo
left a comment
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 is not a regression, it should have changeset and be backported also btw
Signed-off-by: Abhinav Kumar <abhinav@avitechlab.com>
Signed-off-by: Abhinav Kumar <abhinav@avitechlab.com>
d9873cd
|
/patch |
Co-authored-by: Guilherme Gazzo <guilherme@gazzo.xyz>
|
Pull request #36545 added to Project: "Patch 7.8.3" |
|
Sorry, I couldn't do that backport because of conflicts. Could you please solve them? you can do so by running the following commands: after that just run |
Reverts #36156
CORE-1249