Add support for apns-priority key #128
Merged
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
Codecov Report
@@ Coverage Diff @@
## master #128 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 5 5
Lines 259 262 +3
=====================================
+ Hits 259 262 +3
Continue to review full report at Codecov.
|
dplewis
approved these changes
Jul 11, 2019
|
The label |
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.
This is already supported by
node-apnframework but not yet exposed to be usable through this push adapter. It is now possible to set thepriorityfor each notification.When not set,
node-apnuses a priority of 5 as default. This is the minimum value required for background notifications to be able to launch the app in background.