<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal <!--- Clearly outline the goal of the issue and why we are doing it ---> Trigger push & in-app notifications when a supermind request is expiring soon. ## What needs to be done <!--- Clearly detail what needs to be done to achieve the goal set out above ---> Connect the notification work done in #2409 with the expiring soon cronjob work done in #2432. Both of these issues should be completed before starting this one. Probably by linking the push notifs stuff with the `ACTION_SUPERMIND_REQUEST_EXPIRING_SOON` event consumed in SupermindEventStreamsSubscription.php ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> make sure the notifications send ## UX/Design <!--- Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged. ---> n/a ## Personas <!--- Who does this user impact and why (optional) ---> supermind users ## Experiments <!--- Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined. ---> supermind experiment ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [x] in-app notification sent when supermind expiring soon - [x] push notification sent when supermind expiring soon ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments