feat(api): add usage of bridge provider options in send message usecases a… #6062
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
rifont
reviewed
Jul 15, 2024
apps/api/src/app/events/usecases/send-test-email/send-test-email.usecase.ts
Show resolved
Hide resolved
rifont
reviewed
Jul 15, 2024
apps/api/src/app/events/usecases/send-test-email/send-test-email.usecase.ts
Outdated
Show resolved
Hide resolved
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.
What?
When delivering a message to a 3rd party provider in the Worker engine, we need to ensure that the Bridge provider data is given to the Delivery Provider resolver during the delivery flow.
Why? (Context)
Bridge provider data should be used when delivery messages via a Delivery Provider.
Screens
Precedence of provider data resolution
Demonstration of precedence in Provider dashboard (Twilio)
