-
-
Notifications
You must be signed in to change notification settings - Fork 113
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
Order of appearance, or rather, the oldest in the place of the new and old ones dying before no moving all the others. #213
Comments
Hi @johnunclesam! I think this more a product of the each loop showing the array of flash objects. In your component (where you are most likely injecting the flash message service), you can create a new, reversed array based on the queue:
Then in your template, you can update it to:
Now it should be based on the reverse of the queue array and you should get the order you want. |
I face the same issue than @johnunclesam . The problem with your proposed solution @sbatson5 is that it will move the message with the top priority below the lowest priority whereas the expected behavior (IMO) would be a 2 dimensional sort. First by priority, then for messages with the same one, sort from the newest to the oldest. The reversed queue would be sufficient if the priority parameter is not used though. |
My notifications are to the top.
Now, with the same priority, new notifications appear under the old ones.
1
2
3
4
Why?
I wish that the new notifications appeared "above" the other old and older notifications moved down by one step. So when they die they do not move all the others.
4
3
2
1
I'm wrong, or there isn't an option like that?
Thanks in advance.
The text was updated successfully, but these errors were encountered: