Context / Motivation
Delivery-Dashboard often issues multiple requests against Delivery-Service-API (e.g. when populating Landing-Page, or navigating into the Dependencies-Tab of a Component with several (transitive) Component-References.
In some situations, multiple (sometimes all) of such requests will return errors (this can happen, if, for example, Delivery-Service needs to be scaled up). Delivery-Dashboard will display individual Error-Notification-"Snackbars" for each such error. This is quite noisy, and does not help users a whole lot.
Improvement Proposal
Limit amount of Error-Notifications in case of "bursts". There are different approaches that might be evaluated:
- keep track of user-interactions. Group errors for each user-interaction
- heuristically group errors over time (if new error-events occur within a short time-window (maybe 2s), group subsequent errors)
In addition to limiting amount of Error-Notification-Snackbars, consider displaying a log of error-messages that a user can access for debugging purposes (similar to Browsers' web-console, to which one may print using console.log).
Context / Motivation
Delivery-Dashboard often issues multiple requests against Delivery-Service-API (e.g. when populating Landing-Page, or navigating into the Dependencies-Tab of a Component with several (transitive) Component-References.
In some situations, multiple (sometimes all) of such requests will return errors (this can happen, if, for example, Delivery-Service needs to be scaled up). Delivery-Dashboard will display individual Error-Notification-"Snackbars" for each such error. This is quite noisy, and does not help users a whole lot.
Improvement Proposal
Limit amount of Error-Notifications in case of "bursts". There are different approaches that might be evaluated:
In addition to limiting amount of Error-Notification-Snackbars, consider displaying a log of error-messages that a user can access for debugging purposes (similar to Browsers' web-console, to which one may print using console.log).