We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It is good to have option that
<NotificationSystem max=3 ref="notificationSystem" />
My current simulation of it is
if (this._notificationSystem.state.notifications.length > 3) { let allUIds = this._notificationSystem.state.notifications.map( notification => notification.uid ); let keepUIds = this._notificationSystem.state.notifications .slice(3) .map(notification => notification.uid); _.difference(allUIds, keepUIds).map(uid => this._notificationSystem.removeNotification(uid) ); }
The text was updated successfully, but these errors were encountered:
@chungchi300 While this is a good idea, few thing are to be considered.
Setting an upper notification limit is fine.
However if the limit is hit there are few ways to handle this:
Perhaps we can consider which one is the best approach to support and what are the use cases (yours is one of them).
Sorry, something went wrong.
I am also looking for something similar although my ideal approach would be to collapse all notifications into a notification carousel container.
If there are arguments against using this pattern I'd be interested in hearing them.
No branches or pull requests
It is good to have option that
My current simulation of it is
The text was updated successfully, but these errors were encountered: