feat: add prepend(priority) support for toast notifications - #1293
Open
jainmohit535 wants to merge 2 commits into
Open
feat: add prepend(priority) support for toast notifications#1293jainmohit535 wants to merge 2 commits into
jainmohit535 wants to merge 2 commits into
Conversation
jainmohit535
force-pushed
the
feature/priority-toast-1242
branch
2 times, most recently
from
August 1, 2026 10:17
2e2a023 to
308efc9
Compare
jainmohit535
force-pushed
the
feature/priority-toast-1242
branch
from
August 1, 2026 11:01
308efc9 to
cb71d3c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #1242
Adds a per-toast prepend option that inserts a toast before the ones already displayed (or ahead of the waiting queue when limit is set), instead of always appending it.
containerObserver.ts: reorders the active-toasts map on creation when prepend is set; queue.unshift() instead of push() for the limit/queue case.toast.update()merges the original creation options back in, so prepend would otherwise silently persist and incorrectly re-pin an already-placed toast to the front on every update. Covered by a regression test.types.ts: added prepend?: boolean to ToastOptions.pnpm start.