-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
[NV-3053] Migrate from onesignal-node SDK to the official @onesignal/node-onesignal #4635
Comments
HI @LetItRock I would like to work on this. |
Hey @Dhoni77 you are already assigned to an open issue. Let's see if someone is willing to help here, if not we will assign you. |
@Dhoni77 I would like to work on this issue |
@LetItRock Can I work in this issue? |
Hey @anshikavashistha, |
@sakshivbp1812 how things are going? Please let me know if you would love to be un-assigned so we can let someone else to work on this in case you are not able to do so 🙏 |
Hi @scopsy If there is no progress I can take this issue |
@Dhoni77 have assigned you 🙏 |
What?
In the @novu/one-signal package we would like to migrate from using the onesignal-node SDK to the official @onesignal/node-onesignal SDK. Check the documentation about the it here: https://github.com/OneSignal/onesignal-node-api#readme
Why? (Context)
Due to vulnerabilities and un-maintained SDK, we should move from using unofficial onesignal-node SDK.
Definition of Done
The text was updated successfully, but these errors were encountered: