-
Notifications
You must be signed in to change notification settings - Fork 328
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
Local Badge Notification code changes #4926
Local Badge Notification code changes #4926
Conversation
i think if we are bringing in the hierarchy of base notification -> badge notification |
dev/Notifications/BadgeNotifications/BadgeNotificationManager.cpp
Outdated
Show resolved
Hide resolved
dev/Notifications/BadgeNotifications/BadgeNotificationManager.cpp
Outdated
Show resolved
Hide resolved
dev/Notifications/BadgeNotifications/BadgeNotificationManager.cpp
Outdated
Show resolved
Hide resolved
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.
Looking good. I think you can remove the BadgeNotification & BaseNotification types, though? If you need to update NotificationProperties to take a struct of parameters, or have a new ctor that knows "I'm being constructed with all defaults from the set badge notification path" then that's fine.
dev/Notifications/BaseNotifications/BaseNotificationManager.cpp
Outdated
Show resolved
Hide resolved
dev/Notifications/BadgeNotifications/BadgeNotificationManager.cpp
Outdated
Show resolved
Hide resolved
dev/Notifications/BadgeNotifications/BadgeNotificationManager.cpp
Outdated
Show resolved
Hide resolved
dc52aef
to
ba39226
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Issue - #138
API Spec - https://github.com/microsoft/WindowsAppSDK/pull/4823/files#diff-17dae42945b77909c6b45f1e7635b67969b8656882ccca5d20c56fd9ab653d6a
A microsoft employee must use /azp run to validate using the pipelines below.
WARNING:
Comments made by azure-pipelines bot maybe inaccurate.
Please see pipeline link to verify that the build is being ran.
For status checks on the main branch, please use TransportPackage-Foundation-PR
(https://microsoft.visualstudio.com/ProjectReunion/_build?definitionId=81063&_a=summary)
and run the build against your PR branch with the default parameters.