Introduce FcmTopicChannel #231
Merged
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.
This introduces a new
FcmTopicChannel(see #192) that allows sending FCM notifications to topics. It's important to understand why this is implemented as a separate channel and is designed to work a little differently to other notifications that are sent to notifiable models.My general expectation is that this would be used as an on-demand notification where you would dispatch the notification to a topic in real-time.
However - you can still implement
routeNotifiationForFcmTopicon a model and send a notification that way, or set the topic on the message itself. Perhaps this could be expanded to support multiple topics at the same time (if the API allows) but I chose not to implement this here.I updated the docs, cleaned up some additional code and also adopted Pint for consistency going forward.