🚀 Feature: Building up Pushwoosh #1907
Description
🔖 Feature description
Currently the Pushwoosh Push provider is very low built and not up to par with the other services while it could be.
🎤 Why is this feature needed ?
When looking through the documentation I noticed there were many more modes to the studying sent messages and sending messages that come straight out the box with Pushwoosh. Pushwoosh is a very dynamic push provider that doesn't have a main purpose of sending messages, but sending responses on certain signals of receiving a push notification which makes it contrast it's fellow push proivders.
✌️ How do you aim to achieve this?
The best to achieve this is to mess around with the architecture of the Novu push provider base class and allow modularity to what this needs. Mainly, the base function should create a monitor based on the constructor gives, then the extended class would contain many smaller functions that are encapsulated in a larger, main function. This function could use a hash map effect to link commands to the encapsulated functions and call it depending the on the user's end goal.
🔄️ Additional Information
I have already put it push request #1876 to create the base structure for the Pushwoosh provider. Once this provider gets merged to the main branch this work can begin as it is very far behind the other providers.
👀 Have you spent some time to check if this feature request has been raised before?
- I checked and didn't find similar issue
🏢 Have you read the Code of Conduct?
- I have read the Contributing Guidelines
Are you willing to submit PR?
No response