Skip to content

[engine] Tenant control over email digest minds#4990

Ben requested to merge feat/digest-control-m4990 into master

Ticket(s) / Related Merge Requests

Summary of Changes

Give tenant admins control over whether email digests should be dispatched for their network.

Testing Considerations

Bound to https://ben3.oke.minds.io/

Quite tricky to test the actual email as the contents depends on unread notifications, the users top feed and I believe whether you have been send an email previously. Playing with these parameters I have received emails.

Given there are no changes to the actual email, short of a failure to retrieve users (with code that was previously working) this should be safe to consider as working if the tenant is appropriately skipped when running the CLI job (tenant 20 for ben3)

No cluster access required:
  • The toggle appears and can be toggled off and on, with state persisting on reload.
Cluster access required:

I recommend disabling for ALL networks but the network that you are testing for, to avoid email spam.

  • When digest email is disabled, emails DO NOT send via CLI.
  • When digest email is enabled, emails DO send via CLI.

Deployment Considerations

ALTER TABLE `minds_tenant_configs`
    ADD digest_email_enabled boolean DEFAULT TRUE
    AFTER walled_garden_enabled;

Regression Scope

Digest email sending.

Platform Affected (web, mobile, etc)

Web.

Developer Testing Completed

Manual, unit (phpspec, jasmine/karma).

Screenshots / Screen Recording

simplescreenrecorder-2024-07-15_18.29.20

Does this impact

  • Localization
  • Dark/light mode
  • Guest mode

Definition of Done Checklist

  • The Acceptance Criteria has been met
  • Code is tested: Testing includes unit/spec, E2E/automated and manual testing
  • Merge requests description has been filled out
Edited by Ben

Merge request reports