> It seems a fine idea. After a quick skim, the code seems fine. I > wonder thought why you need to notify about ticket changes; surely the > ticket change listener already covers that. > I see are a couple of reasons for this: - There is a case when a listener has to receive change events from different entities, the ticket change event and the version change event. The implementation is much more clean if the listener have to implement only one interface IResourceChangeListener without additionally implementing ITicketChangeListener. - Once upon a time, ITicketChangeListener could be deprecated towards IResourceChangeListener that will simplify core code and decrease number of unit-tests.
Cheers, Andrej -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-dev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
