feat: add reusable empty state components (Closes#138)#396
feat: add reusable empty state components (Closes#138)#396adityasingh511 wants to merge 1 commit into
Conversation
|
@adityasingh511 is attempting to deploy a commit to the Adarsh's projects Team on Vercel. A member of the Team first needs to authorize it. |
MRIARC-08
left a comment
There was a problem hiding this comment.
@adityasingh511 I can’t merge this version. The reusable EmptyState component is useful, but the current integration removes existing behavior.
src/app/notes/page.tsxno longer fetches/searches/displays real notes; it always renders the empty state.src/app/dashboard/analytics/page.tsxhard-codeshasAnalyticsData = false, so analytics are always hidden even when data/components exist.- Focused lint on the touched files reports 20 Prettier errors.
Please keep the existing data-loading flows and show the empty state only when the loaded data is actually empty. Then run the formatter on the touched files.
|
@adityasingh511 Closing this for now because the requested changes have been pending for more than 3 days without a follow-up commit. The reusable EmptyState idea is useful, but this version still changes live dashboard/notes behavior in ways that need correction. Please open a fresh, focused PR once the behavior is preserved and the UI can be manually reviewed. |
Overview
Introduced a highly reusable, minimalist
EmptyStatecomponent to provide consistent, user-friendly feedback in sections where data has not yet been populated.This directly resolves Issue #138 by replacing blank screens with helpful illustrations and clear calls to action.
Key Changes:
src/components/EmptyState.tsx, a flexible component that supports custom SVG icons, descriptive text, and conditionally rendered CTA buttons.Testing
pnpm run buildwith 0 errors.