fix: Cannot read properties of undefined (reading 'format')

[N2D4]

Automated fix by Exterminator

Error: Cannot read properties of undefined (reading 'format')
Source:
Location: Line 0, Col 0

Fix summary

The formatNode function used TypeScript's non-null assertion (node.metadata!.format) on a field that is genuinely undefined at runtime for all incomplete-task nodes and for the synthetic root node created by aggregateNodes, causing a TypeError when the report tree was walked.

Replaced node.metadata!.format with node.metadata?.format ?? "n/a" in the formatNode function. The optional chaining (?.) safely short-circuits to undefined when metadata is absent, and the nullish coalescing (?? "n/a") substitutes a readable placeholder instead of crashing. This fixes the root cause without suppressing the error or altering any other logic.

Changed files

• src/pages/Dashboard.tsx

Summary by CodeRabbit

• Bug Fixes
  • Improved Dashboard component stability by implementing safer metadata handling that gracefully displays a fallback value when metadata is missing, preventing runtime errors during node rendering.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 79672b2 and 88e22a0.

📒 Files selected for processing (1)

• src/pages/Dashboard.tsx

---

📝 Walkthrough

Walkthrough

The formatNode function in Dashboard.tsx now uses optional chaining to safely access metadata properties, providing a fallback "n/a" value when metadata or its format field is undefined, replacing a non-null assertion that could cause runtime errors.

Changes

Cohort / File(s)	Summary
Metadata Handling src/pages/Dashboard.tsx	Modified formatNode header construction to use optional chaining (?.) for metadata access with "n/a" fallback instead of non-null assertion (!), preventing runtime errors when metadata is missing.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 Whiskers twitch with delight so bright,
Optional chaining saves the night!
No more assertions making things break,
A gentle "n/a" for safety's sake. 🥕

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and concisely describes the main change: fixing a specific runtime error by implementing optional chaining and nullish coalescing for the metadata.format property.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch exterminator/fix-r9822n3w

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}