Track topic subscriptions locally#302
Open
xtrinch wants to merge 13 commits into
Open
Conversation
8ab03ce to
ef017f8
Compare
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.
Summary
Add optional local topic subscription tracking so Django can query topic memberships for devices managed through
fcm-django.Why
Firebase's Admin SDK supports subscribing and unsubscribing registration tokens to topics, but it does not expose an API to list topic memberships for a token. This package therefore had no way to answer the request from discussion #263.
What changed
TRACK_TOPIC_SUBSCRIPTIONSsettingFCMDeviceTopicmodel and migrationfcm-djangoImpact
Projects can opt into local topic tracking and query topic membership from Django, while leaving the current behavior unchanged by default.