[ADVAPP-18]: Unify Notification sending for status and delivery tracking #387
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Conflicts: # composer.lock
# Conflicts: # app-modules/notifications/graphql/subscription.graphql # composer.lock
Orrison
reviewed
Dec 21, 2023
app-modules/notification/src/Actions/CreateOutboundDeliverable.php
Outdated
Show resolved
Hide resolved
Orrison
approved these changes
Dec 21, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ticket(s) or GitHub Issue
https://canyongbs.atlassian.net/browse/ADVAPP-18
Technical Description
This PR aims to unify outbound notifications via the new
OutboundDeliverablemodel, which will store pertinent information to the notification, regardless of the channel it is sent via.Types of changes
Screenshots (if appropriate)
Any deployment steps required?
Before contributing and submitting this PR, make sure you have:
developbranch.