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
Currently, when people want to embed the notification center within their app they use the embedding script provided in the application settings screen. This code snippet is similar to google analytics creates an iframe window through which the notification center is displayed thru. On one hand, it's universal but creates weird implementation details when embedding with modern front-end frameworks like react.
What?
Exporting our current widget directly using a react component that the end-user can download from npm, integrate his application id and customize some of the components we provide.
Why?
Currently, when people want to embed the notification center within their app they use the embedding script provided in the application settings screen. This code snippet is similar to google analytics creates an iframe window through which the notification center is displayed thru. On one hand, it's universal but creates weird implementation details when embedding with modern front-end frameworks like react.
What?
Exporting our current widget directly using a react component that the end-user can download from npm, integrate his application id and customize some of the components we provide.
Component API
Additional Hooks:
The text was updated successfully, but these errors were encountered: