Refactor evidence assignee chart for consistent naming conventions

[carhartlewis]

• Updated property names in the AssigneeData interface and related chart configurations from needs_review to needsReview for improved consistency and adherence to camelCase naming conventions.
• Adjusted chart rendering logic to reflect the updated property names, ensuring accurate data visualization.

Summary by CodeRabbit

• Refactor
  • The dashboard’s evidence chart now displays review status information uniformly for improved clarity and reliability, without altering core functionality.
  • This update streamlines the display for a smoother user experience and lays the groundwork for future enhancements.
  • Overall, these refinements provide a more coherent and consistent dashboard experience.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
app	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 1, 2025 1:44am
comp-portal	❌ Failed (Inspect)			Apr 1, 2025 1:44am

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The update refactors the EvidenceAssigneeChart component by renaming the property needs_review to needsReview across its usage. The change affects the AssigneeData interface, the CHART_COLORS object, chart data mapping, chart configuration, and the <Bar> component’s dataKey. The objective is to ensure a consistent camelCase naming convention throughout the file without altering any existing logic or functionality.

Changes

File(s)	Change Summary
apps/app/src/app/[locale]/…/components/evidence-assignee-chart.tsx	Renamed property needs_review to needsReview in the AssigneeData interface, the CHART_COLORS object, the mapping of chartData, the chartConfig object, and the <Bar> component’s dataKey.

Poem

I’m a little rabbit in the code burrow,
Hopping through changes with a joyful glow,
From snake_case trails to camelCase streams,
My whiskers wiggle with refactoring dreams!
Carrots and code—what a delightful day,
With every update, I cheer and say, "Hooray!"
🥕🐰🎉

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 746b859 and ce40d33.

📒 Files selected for processing (1)

• apps/app/src/app/[locale]/(app)/(dashboard)/[orgId]/evidence/(overview)/components/evidence-assignee-chart.tsx (5 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.