empty: Add Empty component#2314
Open
elcoosp wants to merge 1 commit intolongbridge:mainfrom
Open
Conversation
- New `Empty` component for empty-state placeholders - Gallery story showing minimal and full examples - Documentation page following the Kbd structure - Unit tests for basic creation and full configuration - Fixes duplicate `empty_story` module and import entries - Removes unused `h_flex` import
Member
|
Please follow the Shadcn UI style. |
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.
Description
Add
EmptycomponentProblem: There was no built‑in empty‑state placeholder component to use when content areas are empty (e.g., no search results, no items). Developers had to assemble such layouts manually.
Solution:
Empty, a composable empty‑state container supporting an optional icon, title, description, and action button.h_fleximport to keep the codebase clean.All changes are additive and non‑breaking.
Screenshot
Break Changes
None.
How to Test
Ran doc story and test
Checklist
cargo runfor story tests related to the changes.