Update notifications subscription #5189
Closed
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
jinchung
force-pushed
the
@jin/notifications-sub-update
branch
from
cc1bfd0 to
39e708c
Compare
jinchung
force-pushed
the
@jin/notifications-sub-update
branch
5 times, most recently
from
5c0e4d2 to
62aa04d
Compare
initialization Previously, we had to do firebase subscriptions one at a time. With the new API, we need to provide the full state of enabled notifications.
…sting wallet settings
…s back to generic message less
… settings for a wallet
jinchung
force-pushed
the
@jin/notifications-sub-update
branch
from
62aa04d to
e6b33a4
Compare
jinchung
changed the base branch from
develop
to
@jin/notifs-sub-network-settings
jinchung
force-pushed
the
@jin/notifications-sub-update
branch
from
e6b33a4 to
4fbc3ce
Compare
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.
No description provided.