Skip to content

core: frontend: notifications: Group notifications by service - #4589

Merged
patrickelectric merged 2 commits into
bluerobotics:masterfrom
AlejoPm03:group-notifications
Oct 14, 2026
Merged

patrickelectric merged 2 commits into
bluerobotics:masterfrom
AlejoPm03:group-notifications

Conversation

@AlejoPm03

Copy link
Copy Markdown
Contributor

Suggestion to improve the readability of errors, mainly when a service is not working properly

Related to #4204

Currently, errors are shown in a window of 1 minute by default, and the time-ago resolution is also 1 minute, so I believe it is not that important to have a strict temporal order between the notifications of different services.

I think it is more useful to take a quick look at the notifications and see which service notified. If a service has a lot of errors, instead of flooding the notifications, it stays collapsed and shows only the notification types.

notifications.mp4

@joaoantoniocardoso
joaoantoniocardoso requested a review from a team October 14, 2026 14:22

@patrickelectric patrickelectric left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we break this at least in two commits ? one for the components that are under the notifications folder and another one for the store ?

@AlejoPm03
AlejoPm03 force-pushed the group-notifications branch from aeb61e6 to 71fdbae Compare October 14, 2026 17:50
@joaoantoniocardoso joaoantoniocardoso added the move-to-stable Needs to be cherry-picked and move to stable label Oct 14, 2026
@patrickelectric
patrickelectric merged commit a28d51a into bluerobotics:master Oct 14, 2026
11 checks passed
@AlejoPm03
AlejoPm03 deleted the group-notifications branch October 15, 2026 20:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

move-to-stable Needs to be cherry-picked and move to stable

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants