On Mon, Apr 28, 2014 at 10:04 AM, Steffen Hoffmann <[email protected]> wrote: > I guess, that unordered ExtensionsOption has been chosen for change > listeners on purpose. IMO these components shall not implement > side-effects on changed resources, as your description suggests for you > component. Please consider implementing ITicketManipulator [2] to ensure > changes in concert with other ticket changes.
I'm not sure what you mean by "side effects on changes resources." My change listener only writes to its own private tables but it reacts to changes in data managed by MasterTickets. There are reasons that it is more efficient to read the mastertickets relation than rely on the custom blockedby and blocking fields but I can't always know if mastertickets is up to date. ITicketManipulator doesn't seem appropriate here. MasterTickets has one that has done it's validation but it and my plugin both need to react to changes after all validators/manipulators have done their thing. -- 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. For more options, visit https://groups.google.com/d/optout.
