-
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge upstream #12
base: master
Are you sure you want to change the base?
Merge upstream #12
Conversation
adds mutableContent doku entry
Failed tokens can be found with a single `filter` operation over the `registrationTokens` using the 1:1 mapping with response data. Earlier example used `map` + `filter` to achieve the same result.
Update example to find "bad" tokens
…s-message Add fcm_options as allowed params to message object
Normally there is no need to override send URI except for testing
Allow uri override
fix: Gcm InternalServerError should also be retied with exponential-back-off.
dependency upgrades for vulnerabilities flagged by snyk
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Hi @ToothlessGear, your node-gcm repository is an important module for our Parse Server. We have opened several PRs in the past to fix issues and vulnerabilities. Would you be willing to give our organization maintainer / write access to node-gcm, so we don't have to depend on our fork anymore, because we know we can fix vulnerabilities more timely? I have also opened some issues there so we can make sure vulnerabilities are fixed faster and releases are more robust. |
Merge upstream 1.0.4
The parse-server-push-adapter points to
@parse/node-gcm": "1.0.2"
, so I assume even when merging this PR, it won’t have any effect. We may have to add our own tag and point to that?