docs(toast): add usage guide covering duration, density, quiet mode, and actions#344
Open
jabir-dev788 wants to merge 1 commit into
Open
docs(toast): add usage guide covering duration, density, quiet mode, and actions#344jabir-dev788 wants to merge 1 commit into
jabir-dev788 wants to merge 1 commit into
Conversation
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
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.
Summary
Adds docs/components/toast.md, documenting the public API and behavioral
contracts of the toast system (useToast / ToastProvider) that previously
only existed as inline comments in toast-provider.tsx.
Covers
Verification
Every documented behavior was cross-checked against toast-provider.tsx
source and toast-provider.test.tsx assertions to avoid drift. No source
files were modified — documentation only.
Scope note
The issue's general guidelines mention 95% test coverage; this is a
documentation-only PR with no code changes, so no new tests were added,
per the issue's own "Suggested execution" section (snippets verified by
mirroring existing test patterns instead).
Checks