Added listeners to create subscriptions

Author: schwuk

README.md

@@ -70,6 +70,9 @@ tickets and which are not.
 * Notifications – if you have configured Trac to email ticket notifications
 then comment notifications will just work!
 
+ * Subscriptions – Authors of changesets and attachments, and anyone who
+creates a comment are subscribed to notifications of comments; to have changeset authors automatically subscribed, your repositories must be configured for [synchronisation](http://trac.edgewall.org/wiki/TracRepositoryAdmin#Synchronization) with Trac
+
 Screenshots
 -----------
 

code_comments/subscription.py

@@ -1,8 +1,10 @@
 from trac.admin import IAdminCommandProvider
-from trac.attachment import Attachment
+from trac.attachment import Attachment, IAttachmentChangeListener
 from trac.core import Component, implements
-from trac.versioncontrol import RepositoryManager, NoSuchChangeset
+from trac.versioncontrol import (
+    RepositoryManager, NoSuchChangeset, IRepositoryChangeListener)
 
+from code_comments.api import ICodeCommentChangeListener
 from code_comments.comments import Comments
 
 
@@ -200,3 +202,27 @@ def _do_seed(self):
         comments = Comments(None, self.env).all()
         for comment in comments:
             Subscription.from_comment(self.env, comment)
+
+
+class SubscriptionListeners(Component):
+    """
+    Automatically creates subscriptions for attachments, changesets, and
+    comments.
+    """
+    implements(IAttachmentChangeListener, IRepositoryChangeListener,
+               ICodeCommentChangeListener)
+
+    # IAttachmentChangeListener methods
+
+    def attachment_added(self, attachment):
+        Subscription.from_attachment(self.env, attachment)
+
+    # IRepositoryChangeListener methods
+
+    def changeset_added(self, repos, changeset):
+        Subscription.from_changeset(self.env, changeset)
+
+    # ICodeCommentChangeListener methods
+
+    def comment_created(self, comment):
+        Subscription.from_comment(self.env, comment)

todo.md

@@ -32,9 +32,9 @@ Need to figure out how to handle blanket subscriptions.
 
 ## Listeners
 
-- [ ] comments_created - create a subscription for the comment author
-- [ ] attachment_added - create a subscription for the attachment author
+- [x] comments_created - create a subscription for the comment author
+- [x] attachment_added - create a subscription for the attachment author
 - [ ] attachment_deleted - remove all subscriptions for the attachment (should we also remove all comments?)
 - [ ] attachment_reparented - update all subscriptions for the attachment
-- [ ] changeset_added - create a subscription for the changeset author
+- [x] changeset_added - create a subscription for the changeset author
 - [ ] changeset_modified - update the subscription (author?)