Skip to content

Conversation

@timyates
Copy link
Contributor

When GuildMemberServices save or delete is called from the GuildMemberController, we want to send an email.

However when these methods are called from the GuildServices we don't, as this email is sent by GuildServices.

This PR adds a flag as to whether an email should be sent, and fixes the mockito in the tests to ensure a single email is sent

Closes #2549

When GuildMemberServices save or delete is called from the GuildMemberController, we want to send an email.

However when these methods are called from the GuildServices we don't, as this email is sent by GuildServices.

This PR adds a flag as to whether an email should be sent, and fixes the mockito in the tests to ensure a single email is sent
@timyates timyates added bug Something isn't working server labels Jul 12, 2024
@timyates timyates requested a review from mkimberlin July 12, 2024 15:30
@timyates timyates self-assigned this Jul 12, 2024
@mkimberlin mkimberlin merged commit df3f1cf into develop Aug 6, 2024
@mkimberlin mkimberlin deleted the bugfix-2549/reduce-emails-for-guild-changes branch August 6, 2024 17:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working server

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Too many emails are being sent with changes via the GuildController

3 participants