Test(dashboard): handle empty error fallbacks safely#5369
Conversation
|
🚨 Hey @diksha78dev, the CI Pipeline is failing on this PR and it has been marked as Please fix the issues before this can be reviewed. Here's how: 1. Run checks locally before pushing: npm run format:check # Check Prettier formatting
npm run lint # Run ESLint
npm run typecheck # TypeScript type check
npm run test # Run unit tests (Vitest)
npm run build # Verify production build passes2. Auto-fix common issues: npm run format # Auto-fix formatting with Prettier
npm run lint -- --fix # Auto-fix lint errors where possible3. Check the full failure log here: Once you push a fix and the CI passes, the |
31ca2b9 to
12556de
Compare
|
🎉 Congratulations @diksha78dev! Your PR has been successfully merged. 🚀 Thank you for contributing to CommitPulse. Your work helps us build a better tool for the community.
Keep building! 💻✨ |
Description
Fixes #4199. Resolves a crash in the dashboard error boundary component when rendering null, undefined, empty, or malformed error objects by ensuring proper fallback checks.
Pillar
Visual Preview
N/A — Logic and testing update only. No visual elements changed.
Checklist before requesting a review:
CONTRIBUTING.mdfile.npx vitest run "app/(root)/dashboard/error.empty-fallback.test.tsx" "app/(root)/dashboard/error.test.tsx").npm run formatandnpm run lintlocally and resolved all errors (CI will fail otherwise).feat(themes): ...,fix(calculate): ...).README.mdif I added a new theme or URL parameter. (N/A — no theme or URL parameters added)