-
Notifications
You must be signed in to change notification settings - Fork 4k
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
feat: π Feature β Add Web PushAPI support as Push Provider #3385
base: next
Are you sure you want to change the base?
Conversation
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.
Great job adding a new provider, I left a couple of questions regarding topics I was not sure about.
Any movement on this @johnmarksilly |
@johnmarksilly |
@inveve @jainpawan21 @djabarovgeorge See conflict resolutions. @djabarovgeorge If you have strong opinions about the private/public key credentials let me know and I'll update, but IMO I believe that these will be useful to other devs and are more clear than using other properties. I understand this is hidden from end-users, but devs may find it useful. |
@jainpawan21 Is this ready for merge? |
Any update @jainpawan21 |
@djabarovgeorge WDYT what should we do with this PR as there are lot of merge conflicts due to inactivity. |
I can go through and resolve the conflicts tomorrow. Every time I get it ready though, it gets forgotten! |
Wondering if this will ever get merged π€ |
What change does this PR introduce?
Add a new push provider to support the web PushAPI standard
Why was this change needed?
Support for alternative push method for browsers when external vendors aren't used.
Closes #3459
Other information (Screenshots)
N/A