stable

Clone or download

Read-only

chore: Introduce strategy to deal with recipient removal

The current implementation of RecipientManager is a suite of different patterns applied one after another. Let's make it clear and easier to grasp with chain of responsability pattern. This commit also brings the logger a little bit deeper in the stack to get more information on how and when users are removed from notification. Part of: story #10469 choose if I receive a notification when I create/update something Change-Id: If4f0b46c469151527507c3df14dc0d0f022a5191

Modified Files

Name
M plugins/tracker/include/Tracker/Artifact/Changeset/PostCreation/EmailNotificationTask.php +1 −1 Go to diff View file
A plugins/tracker/include/Tracker/Notifications/GetUserFromRecipient.php +31 −0 Go to diff View file
A plugins/tracker/include/Tracker/Notifications/RecipientRemovalStrategy.php +35 −0 Go to diff View file
M plugins/tracker/include/Tracker/Notifications/RecipientsManager.php +19 −61 Go to diff View file
A plugins/tracker/include/Tracker/Notifications/RemoveRecipient/RemoveRecipientWhenTheyAreInCreationOnlyMode.php +66 −0 Go to diff View file
M plugins/tracker/tests/unit/Tracker/Artifact/Changeset/PostCreation/NotifierCustomSenderTest.php +2 −1 Go to diff View file
M plugins/tracker/tests/unit/Tracker/Notifications/RecipientsManagerTest.php +17 −16 Go to diff View file