Releases: EasyAbp/NotificationService
Releases · EasyAbp/NotificationService
3.2.0
3.1.0
3.0.0
2.0.0
Important Changes
Breaking Changes
- Private message notifications no longer have to be sent by (and are by default not sent by) the creator of the notification.
- To be valid, the target user's phone number and email address must be confirmed (PhoneNumberConfirmed and EmailConfirmed).
- The notification for failed sending no longer automatically retries. The retry function has not yet been implemented in this module, but you can recreate these notifications yourself.
- The
RetryNotificationId
property of the Notification entity has been renamed toRetryForNotificationId
in preparation for implementing the notification send retry function. - Private message notifications are sent using the integration service instead of distributed events.
Others
- A new
INotificationIntegrationService
integration service is now available, which you can use to create notifications instead of using the distributed event bus. It additionally provides a "QuickSend" method to support creating notifications and executing the sending of the notification within the user thread.
What's Changed
IdentityUserPhoneNumberProvider
should return only confirmed phone numbers by @gdlcf88 in #19- Introduce
NotificationIntegrationService
andINotificationManager
by @gdlcf88 in #20 - Improve exception handling by @gdlcf88 in #21
- Fix the notification management page by @gdlcf88 in #22
- The user's email to be sent should be confirmed by @gdlcf88 in #23
- Upgrade to the PM module v2.0.0 and add a
SendFromCreator
arg by @gdlcf88 in #24
Full Changelog: 1.1.0...2.0.0
1.0.0
0.7.0
What's Changed
- Rename
Test
toTests
for test projects by @gdlcf88 in #8 - Upgrade to PM module 1.5.0 by @gdlcf88 in #9
- Fix typo of the PM abstractions module name by @gdlcf88 in #10
- Introduce WeChat Official notification service provider by @gdlcf88 in #11
New Contributors
Full Changelog: 0.6.0...0.7.0