Stack Toast Notifications with a Queue Limit
Cap the visible toasts at 3 and queue the rest so a burst of 10 notifications does not cover the screen.
Task
Add const queue = new ToastQueue({ maxVisible: 3, duration: 5000 }); queue.push({ message, type: 'success' }); so the interface remains usable and accessible under the edge cases that manual testing skips.
When to use this
A screen reader user reports the page is unusable because const queue = new ToastQueue({ maxVisible: 3, duration: 5000 }); queue.push({ message, type: 'success' }); was never implemented, flagged in a support ticket.
Prerequisites
- A frontend component or page in the codebase
- A build with the relevant framework configured
Steps
1. Configure const queue = new ToastQueue({ maxVisible: 3, duration: 5000 }); queue.push({ message, type: 'success' }); in the project configuration file with the recommended defaults.
const queue = new ToastQueue({ maxVisible: 3, duration: 5000 }); queue.push({ message, type: 'success' });
Expected output: The configuration is accepted and const queue = new ToastQueue({ maxVisible: 3, duration: 5000 }); queue.push({ message, type: 'success' }); runs without errors on the first invocation.
2. Run the check locally to verify const queue = new ToastQueue({ maxVisible: 3, duration: 5000 }); queue.push({ message, type: 'success' }); produces the expected result before pushing.
pnpm test
Expected output: Local run matches CI behavior; no surprises after push.
3. Add the gate to the CI pipeline so const queue = new ToastQueue({ maxVisible: 3, duration: 5000 }); queue.push({ message, type: 'success' }); blocks merge on failure.
- name: Run add toast queue stacking
run: pnpm test
Expected output: Pull requests with failing const queue = new ToastQueue({ maxVisible: 3, duration: 5000 }); queue.push({ message, type: 'success' }); are blocked from merging.
Troubleshooting
Problem
The check passes locally but fails in CI
Solution
Pin dependency versions and the runtime to match CI exactly; reproduce with the same Docker image or act.
Problem
Configuration is rejected with a schema error
Solution
Check the tool version matches the config schema; older versions may not support newer fields.
Limitations
- The gate only runs on events that trigger the workflow; locally pushed commits bypass it.
- Configuration drift is possible if someone edits settings outside version control.
Handle the edge case
Start by measuring the problem. Cap the visible toasts at 3 and queue the rest so a burst of 10 notifications does not cover the screen. The most common mistake is adding the gate without first confirming it catches the issue you care about. Run const queue = new ToastQueue({ maxVisible: 3, duration: 5000 }); queue.push({ message, type: ‘success’ }); against the current codebase and inspect the output before wiring it into CI.
const queue = new ToastQueue({ maxVisible: 3, duration: 5000 }); queue.push({ message, type: 'success' });Test with real tools
Once the gate is in place, make failures actionable. A failing const queue = new ToastQueue({ maxVisible: 3, duration: 5000 }); queue.push({ message, type: ‘success’ }); should point to the exact file and line, not a generic error. Pin the tool version in the lockfile so a upstream release does not silently change behavior. Review the gate output in every pull request just like a test result.