feat(notification): expose providers #14068
Closed
+22
−3
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.
Summary
What
Makes notification providers available to query.graph, also exposes the getProviderForChannel method for convenience
Why
There isn't currently a way to retrieve notification providers, which is necessary to implement features or retrieve data that are provider specific. For example I'm building a plugin to have a friendly UI interface for wiring up notifications and to be able to retrieve/store generic templates you need the list of providers to choose from.
How
The NotificationProvider model was added to the notification's module MedusaService, which is exactly what the fullfilment and tax modules do to make providers queryable.
Checklist
Please ensure the following before requesting a review:
yarn changesetand follow the prompts