feat: add field to webpush options to allow for Declarative Web Push messages - #2893
feat: add field to webpush options to allow for Declarative Web Push messages#2893acrobid wants to merge 4 commits into
Conversation
Sorry, something went wrong.
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
Sorry, something went wrong.
|
Hey @acrobid, thank you for your contribution we appreciate it! I don't think this feature is currently supported by the BE REST service so adding it to the SDK wouldn't address the issue. Hey @chong-shao could you add more context here, please? Thank you! |
Sorry, something went wrong.
|
Yes, please refer to #2892 (comment) for context |
Sorry, something went wrong.
|
My understand is that declarative web push has now landed in the specifications. |
Sorry, something went wrong.
See issue here:
#2892
Spec proposal:
See https://pr-preview.s3.amazonaws.com/w3c/push-api/pull/385.html#declarative-push-message
API Changes
This change allows for a new optional property in the webpush options, and will not affect existing projects.