Creating Notification Capability on Scooped Backend #48
Conversation
This file contains hidden or 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
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.
Overview
Integrate fcm-django into our database so that we can use Firebase Cloud Messaging systems to allow notifications on our frontend devices. We do this by creating an FCM device for each user when provided an FCM registration token. This allows us to use our Firebase server to send notifications to the frontend.
Changes Made
Added a route for FCM devices. Also added a route for sending a message to another user, which you specify with an "id" in the route.
Test Coverage
Unfortunately, we were unable to test this as of yet, as front end needs to communicate with Firebase in order to get an FCM registration token.