You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm always frustrated when I need to use the Notification API and PushManager API in the ng-web-apis. The library currently lacks support for these APIs. This forces me to make some workarounds, using non-ideal techniques.
Describe the solution you'd like
I'd like to request the addition of support for the Notification API and PushManager API in the library. It would be cool if these APIs could be accessed through an injectable token in the constructor like a NAVIGATOR or a WINDOW, that allows for more maintainable code.
Describe alternatives you've considered
I'm currently using the makeshift approach:
constructor(@Inject(WINDOW)privatereadonlywindow: Window){}// acces PushManager APIthis.window['PushManager']// check Notification API supportwindowNotification='Notification'inthis.window||this.window['Notification'];
However, this workaround bypasses the advantages of dependency injection and can lead to less maintainable code.
The text was updated successfully, but these errors were encountered:
🚀 Feature request
Is your feature request related to a problem?
I'm always frustrated when I need to use the Notification API and PushManager API in the ng-web-apis. The library currently lacks support for these APIs. This forces me to make some workarounds, using non-ideal techniques.
Describe the solution you'd like
I'd like to request the addition of support for the Notification API and PushManager API in the library. It would be cool if these APIs could be accessed through an injectable token in the constructor like a
NAVIGATOR
or aWINDOW
, that allows for more maintainable code.Describe alternatives you've considered
I'm currently using the makeshift approach:
However, this workaround bypasses the advantages of dependency injection and can lead to less maintainable code.
The text was updated successfully, but these errors were encountered: