-
Notifications
You must be signed in to change notification settings - Fork 17.2k
feat: add id, groupId, and groupTitle support for Windows notifications #50328
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
Merged
VerteDinde
merged 9 commits into
electron:main
from
bitdisaster:notification-id-for-windows
Apr 10, 2026
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
edd5e4f
feat: allow to set id and groupId
bitdisaster f524774
feat: use Id's without hash but check length
bitdisaster 812dcf2
feat: adds visual grouping via groupTitle
bitdisaster c59f254
test: tests added for id, groupId and groupTitle
bitdisaster 48532c7
fix: unused vars on Mac and Linux
bitdisaster 33a8cd7
fix: remove redundant parameter
bitdisaster 8cb1893
fix: add doc links for id and group
bitdisaster cecf9a9
fix: throw if groupId is missing
bitdisaster 8cd36bc
fix: test
bitdisaster File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back 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.
We're parsing the options dict twice — once here via
PeekNext+ConvertFromV8to validate, and then again inside the Notification constructor. Imo that's a bit redundant and fragile since the two parse sites could diverge.The
gin::Dictionary(nullptr)+ theIsEmpty()|| IsUndefined() || ConvertFromV8(...)` conditional is also a bit hard to follow — the first two branches fall through into the body with a null-initialized dictionary, which feels like it shouldn't work.Could we instead construct the Notification first and then validate the already-parsed members before returning the handle? Something like:
That way we validate against the actual values that'll be used at
Show()time, and there's a single parse path for the options.I recognize the downside here that we construct the object before potentially discarding it on the error path, but the constructor is side-effect-free, and
CreateHandle + return {}is already the pattern used for the "app not ready" early return above, so it should be safe?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