Changes between Version 5 and Version 6 of TracDev/NotificationApi

Timestamp:

Jul 31, 2015, 2:17:33 PM (9 years ago)

Author:

figaro

Comment:

Cosmetic changes, added link to Open questions

TracDev/NotificationApi

@@ -1 @@
-[[PageOutline(2-3)]]
+[[PageOutline(2-3,Contents)]]
 
 = Trac Notification API
 
-== New API
-''(since Trac 1.1.3)''
+== Current API
 
-The new API keeps the `IEmailSender` extension point and the `NotificationSystem` component almost unchanged from the [#OldAPI old API], but deprecates the entire `Notify` hierarchy.
+Since Trac 1.1.3.
+
+The current API keeps the `IEmailSender` extension point and the `NotificationSystem` component almost unchanged from the [#PreviousAPI previous API], but deprecates the entire `Notify` hierarchy.
 
 It is replaced by a new class hierarchy. An instance of such a class contains all known data about an event that requires sending notifications:
@@ -16 +17 @@
 
 === !NotificationEvent
+
 Contains the following properties:
 * `realm`: a string of the affected resource realm (e.g. `'ticket'` or `'wiki'`)
@@ -24 +26 @@
 
 === !TicketChangeEvent
+
 * `realm` is 'ticket'.
 * Known values for `category` are `'created'`, `'changed'`, `'attachment added'` and `'attachment deleted'`.
@@ -33 +36 @@
 
 === !BatchTicketChangeEvent
+
 * `realm` is 'ticket'.
 * `category` is 'batchmodify'.
@@ -41 +45 @@
   * `action`: a ticket action controller action
 
-== Old API
-''(since Trac 0.7, deprecated since Trac 1.1.3)''
+See also: /TracDev/Proposals/AdvancedNotification/NotificationApi#OpenQuestions
+
+== Previous API
+
+Since Trac 0.7, deprecated since Trac 1.1.3.
 
 The original notification API consisted mainly of a class hierarchy: