Open banshiAnton opened 8 months ago
HI ! Any plan to merge this great PR in the base repo ?
@banshiAnton first of all sorry for the delay on the review and many thanks for your contribution. I think it can help to evolve the repo to better integration with FCM/GCM.
I've made some comments on your code that would help to make this repo better mantainable.
If possible, could you please add the corresponding documentation for the new options to the Readme.md, and perhaps include the examples from this pull request? It would be really helpful!
Hi @miqmago i have updated README.md but i can't see any comments for code
I've made some comments on your code that would help to make this repo better mantainable.
Hi @banshiAnton it's quite strange you can't see my comments... Don't appear to you on this thread? I can se them just few messages before this one, as a review... Also if you open https://github.com/appfeel/node-pushnotifications/pull/194/files?diff=split&w=1 I can see my comments there.
I've added a ping on one of them to see if you receive a message on the first one. Just let me know if it works, I will ping on every comment then.
Ok @banshiAnton I've just noticed that I had to submit my review... 🤦🏼♂️🤦🏼♂️ You should see it now.
Hello, I just want to thank you for all your great work, as the deprecation of the old http fcm is fast approaching. I hope you have enough time to finish the new major version. Thanks again.
From my side seems all fine. @alex-friedl could you please confirm if is it ok for you? @banshiAnton could you please solve package conflicts?
@miqmago @banshiAnton Generally looks good to me as well. @banshiAnton When you get to rebasing the branch, could you also take a look at the open conversations in the PR? :)
Thanks everyone for your great work here! This will be good to have so that we aren't left in a broken state in June.
@banshiAnton Nice work! I believe you're missing an export reference in the file lib/push_notifications.js
. It currently looks like:
module.exports = PN;
module.exports.WEB = _constants.WEB_METHOD;
module.exports.WNS = _constants.WNS_METHOD;
module.exports.ADM = _constants.ADM_METHOD;
module.exports.GCM = _constants.GCM_METHOD;
module.exports.APN = _constants.APN_METHOD;
You will need to add module.exports.FCM
there as well.
@banshiAnton are you available to make pull from master, resolve conflicts and push again to your branch? This would help with merging this important feature.
@miqmago 👋🏽 I left a couple of comments with some important bug fixes for this PR. My review comment is still marked as "pending" so unsure if @banshiAnton is able to see it. Specifically:
module.exports.FCM = _constants.FCM_METHOD
needs to be added to the bottom of lib/push_notifications.js
, andsrc/utils/fcmMessage.js
needs to be fixed so it reads androidMessage.ttl = androidMessage.timeToLive
(i.e. timeToLive
should not be snake-cased here). In addition, the * 1000
multiplier could cause issues as it looks like this value is expected to be in seconds, not ms per the FCM docsIn the linked issue in node-gcm, the OP assumes that since it was deprecated on June 20, 2023, it will be discontinued on June 20, 2024, but Google doesn't actually give a day, only a month. It could as easily be June 1, so we're 3 weeks away.
Since we haven't heard from @banshiAnton since January, I forked the fork, updated it with current master
, and addressed the feedback by @nsakaimbo
I have opened a PR here: https://github.com/appfeel/node-pushnotifications/pull/205
Just to be clear, I'm not trying to steal credit in any way, and I don't pretend to have much domain knowledge nor a full grasp of all of the preceding changes. But my company depends on this library and will be in serious trouble without the update.
Deadline is fast approaching on this. When is this going to be merged and is there anything the rest of us can do to help expedite?
Any plan to merge this PR?
Cause: GCM method which use old firebase api (will be deprecated )
rawPayload
option for Apns methodfcm_notification
object param for FCM/GCM android notification sendUsage:
Fcm object: