Fix lint issues in dashboard.

[sbansal1999]

Summary by CodeRabbit

• Refactor

  • Improved code clarity and consistency by adding explicit braces to single-line conditional statements across multiple dashboard components.
  • Updated array creation syntax for rendering placeholder cards in loading states.
  • Removed unused imports to streamline code.

• Chores

  • Cleaned up import statements by removing unused dependencies.

No user-facing functionality or behavior has changed.

[vercel]

@sbansal1999 is attempting to deploy a commit to the Databuddy Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

The changes across multiple components standardize the use of explicit curly braces around single-line conditional statements, converting them into multi-line blocks for clarity and consistency. Some minor code cleanups are also present, such as removing unused imports and adjusting array creation syntax. No logic, control flow, or exported/public entity signatures are altered.

Changes

Cohort / File(s)	Change Summary
Explicit Braces for Single-Line Conditionals (Errors Section) apps/dashboard/app/(main)/websites/[id]/errors/_components/error-table-columns.tsx, .../error-trends-chart.tsx, .../errors-page-content.tsx, .../top-error-card.tsx, .../utils.ts	All single-line conditional statements are refactored to use explicit curly braces, converting them into multi-line blocks. No logic or control flow is changed.
Explicit Braces for Single-Line Conditionals (Funnels Section) apps/dashboard/app/(main)/websites/[id]/funnels/_components/edit-funnel-dialog.tsx	All single-line early return conditionals are rewritten with explicit curly braces for clarity; no logic or flow changes.
Explicit Braces for Single-Line Conditionals (Goals Section) apps/dashboard/app/(main)/websites/[id]/goals/_components/edit-goal-dialog.tsx	All single-line early return conditionals are rewritten with explicit curly braces for clarity; no logic or flow changes.
Minor Array Construction and Formatting Adjustments (Goals Section) .../goal-analytics.tsx, .../page.tsx	Array creation syntax changed from [...Array(3)] to [...new Array(3)] for skeleton loading cards; number formatting conditionals refactored to use explicit braces.
Unused Import Removal apps/dashboard/app/(main)/websites/[id]/goals/_components/delete-goal-dialog.tsx	Removes unused Target icon import; no other changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Poem

In lines of code where braces grow,
The garden’s neat, the logic flows.
No secrets changed, no paths anew,
Just tidy blocks for clearer view.
With arrays and imports set just right,
This bunny hops off—code shining bright! 🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 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 e21c29e and 5dc3f20.

📒 Files selected for processing (10)

• apps/dashboard/app/(main)/websites/[id]/errors/_components/error-table-columns.tsx (1 hunks)
• apps/dashboard/app/(main)/websites/[id]/errors/_components/error-trends-chart.tsx (1 hunks)
• apps/dashboard/app/(main)/websites/[id]/errors/_components/errors-page-content.tsx (3 hunks)
• apps/dashboard/app/(main)/websites/[id]/errors/_components/top-error-card.tsx (1 hunks)
• apps/dashboard/app/(main)/websites/[id]/errors/_components/utils.ts (1 hunks)
• apps/dashboard/app/(main)/websites/[id]/funnels/_components/edit-funnel-dialog.tsx (11 hunks)
• apps/dashboard/app/(main)/websites/[id]/goals/_components/delete-goal-dialog.tsx (1 hunks)
• apps/dashboard/app/(main)/websites/[id]/goals/_components/edit-goal-dialog.tsx (9 hunks)
• apps/dashboard/app/(main)/websites/[id]/goals/_components/goal-analytics.tsx (2 hunks)
• apps/dashboard/app/(main)/websites/[id]/goals/page.tsx (1 hunks)

🔇 Additional comments (14)

apps/dashboard/app/(main)/websites/[id]/errors/_components/utils.ts (1)

5-7: LGTM! Consistent brace formatting applied.

The explicit curly braces around conditional blocks improve code consistency and readability. The logic and control flow remain unchanged.

Also applies to: 10-12, 16-18, 21-23

apps/dashboard/app/(main)/websites/[id]/errors/_components/top-error-card.tsx (1)

13-15: LGTM! Consistent guard clause formatting.

The explicit braces around the null check improve code consistency with the rest of the codebase.

apps/dashboard/app/(main)/websites/[id]/errors/_components/error-table-columns.tsx (1)

133-141: LGTM! Consistent conditional block formatting.

The explicit braces around the device type conditional improve code consistency and maintainability.

apps/dashboard/app/(main)/websites/[id]/errors/_components/error-trends-chart.tsx (1)

158-160: LGTM! Consistent number formatting conditional blocks.

The explicit braces around the number formatting conditionals maintain consistency with the codebase style guidelines.

Also applies to: 161-163

apps/dashboard/app/(main)/websites/[id]/errors/_components/errors-page-content.tsx (1)

46-48: LGTM! Consistent conditional formatting applied.

The explicit braces around conditional blocks in the filter logic and useMemo hooks improve code consistency and readability. All logic remains unchanged.

Also applies to: 186-188, 198-200

apps/dashboard/app/(main)/websites/[id]/funnels/_components/edit-funnel-dialog.tsx (3)

96-98: LGTM! Consistent brace usage for early returns.

These changes standardize the use of explicit curly braces around single-line conditional early returns, improving code consistency and likely addressing ESLint curly rule violations. The logic remains unchanged while enhancing readability.

Also applies to: 137-139, 155-157, 172-174

---

191-193: LGTM! Proper formatting for guard clauses.

The conversion of single-line conditional returns to multi-line blocks with braces follows consistent formatting standards. This makes the codebase more maintainable and adheres to linting rules.

Also applies to: 199-201, 220-222, 238-240

---

255-257: LGTM! Standardized conditional formatting.

All conditional guard clauses now use explicit braces, creating consistency across the component. This addresses linting issues while maintaining the same functional behavior.

Also applies to: 296-298, 324-326, 349-351, 359-361

apps/dashboard/app/(main)/websites/[id]/goals/_components/delete-goal-dialog.tsx (1)

3-3: LGTM! Cleaned up unused import.

Removing the unused Target icon import reduces bundle size and addresses linting warnings about unused imports. Good cleanup!

apps/dashboard/app/(main)/websites/[id]/goals/_components/goal-analytics.tsx (2)

30-30: LGTM! Consistent array construction.

Using new Array(3) instead of Array(3) follows consistent constructor usage patterns and likely addresses linting preferences for explicit constructor calls.

---

82-87: LGTM! Standardized conditional formatting.

Converting single-line conditional returns to use explicit braces improves consistency with the rest of the codebase and addresses linting rules requiring braces around conditional statements.

apps/dashboard/app/(main)/websites/[id]/goals/page.tsx (1)

35-35: LGTM! Consistent array constructor usage.

Standardizing array creation with new Array(3) maintains consistency with similar changes across the codebase and addresses linting preferences for explicit constructor calls.

apps/dashboard/app/(main)/websites/[id]/goals/_components/edit-goal-dialog.tsx (2)

74-76: LGTM! Consistent brace formatting for early returns.

These changes standardize conditional guard clauses to use explicit braces, improving code consistency across the component and addressing ESLint formatting rules.

Also applies to: 94-96, 110-112, 128-130

---

145-147: LGTM! Proper conditional statement formatting.

Converting single-line returns to multi-line blocks with braces creates consistency with the rest of the codebase and follows established linting standards for conditional statements.

Also applies to: 186-188, 214-216, 239-241, 272-274

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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.

[sbansal1999]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[sbansal1999]

Closing in favour of #43.