-
Notifications
You must be signed in to change notification settings - Fork 3
feat(notifications): handle on click for browser notifications #357
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
feat(notifications): handle on click for browser notifications #357
Conversation
M-5269 browser notification click should go to notification
Clicking on a browser notification should take you directly to the notification in the channel or in the email |
6203112 to
fb306f1
Compare
5e5b6ba to
42fd90f
Compare
fb306f1 to
06a750d
Compare
06a750d to
b37c9be
Compare
…browser-notification-click-should-go-to-notification
sedson
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.
lgtm with question
| replaceOrInsertSplit({ type: 'email', id: targetId }); | ||
| break; | ||
| handle?.goToLocationFromParams({ | ||
| messageId, |
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.
is this for both email and channel? I don't think those are the right param names for channels - idk about email. it's ugly but we should be importing the URL_PARAM constants from the blocks here i think?
| n.eventItemId | ||
| ) | ||
| ) | ||
| .with( |
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.
damn ok new lib
Adds support for clicking on a browser / platform notification to open the notification. Centralizes some of the sprawling logic for doing this within the app.