🐛 (reports) fix reports page having empty blocks

[MatissJanis]

Fixes #3559

Not exactly a perfect patch, but a workable short-term solution until I get the dashboards feature finished off.

[coderabbitai]

Walkthrough

The pull request modifies the Overview component in Overview.tsx by introducing a filtering step to the baseLayout array construction. It conditionally excludes certain widgets based on the isDashboardsFeatureEnabled feature flag and the customReportMap. Additionally, it updates the layout logic to add a 'spending-card' widget if the spendingReportFeatureFlag is enabled and the dashboards feature is not. This change enhances the conditional display of widgets based on feature flags.

Changes

Files	Change Summary
packages/desktop-client/src/components/reports/Overview.tsx	Updated baseLayout array construction to filter widgets based on isDashboardsFeatureEnabled and customReportMap. Added conditional logic for 'spending-card' widget based on feature flags.

Assessment against linked issues

Objective	Addressed	Explanation
Prevent empty spaces when creating new custom reports after deletion (related to #3559)	✅

Possibly related PRs

• ✨ (dashboards) ability to save filters & timeframes on spending widgets #3432: This PR involves changes to the Spending component, which may interact with the layout logic in the Overview component, particularly regarding how spending widgets are displayed based on feature flags.
• 🐛 (reports) deleting custom report should remove it from the dashboard #3469: This PR introduces a feature flag check in the CustomReportListCards component, which is relevant as the main PR also modifies layout logic based on feature flags, potentially affecting how custom reports are rendered in the dashboard.
• 🐛 fix custom reports crashing when opening table #3484: Although primarily focused on fixing crashes in the CustomReport component, the changes in state management could relate to how reports are handled in the Overview component, especially in terms of rendering based on the presence of custom reports.

Suggested labels

sparkles: Merged

Suggested reviewers

• carkom
• MikesGlitch

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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 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.

[netlify]

✅ Deploy Preview for actualbudget ready!

Name	Link
🔨 Latest commit	d2f3c51
🔍 Latest deploy log	https://app.netlify.com/sites/actualbudget/deploys/67002f754971db00087e35de
😎 Deploy Preview	https://deploy-preview-3566.demo.actualbudget.org
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[github-actions]

Bundle Stats — desktop-client

Hey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle.

As this PR is updated, I'll keep you updated on how the bundle size is impacted.

Total

Files count	Total bundle size	% Changed
9	5.29 MB → 5.29 MB (+157 B)	+0.00%

Changeset

File	Δ	Size
src/components/reports/Overview.tsx	📈 +209 B (+1.30%)	15.71 kB → 15.91 kB
src/components/BankSyncStatus.tsx	📉 -52 B (-2.68%)	1.89 kB → 1.84 kB

View detailed bundle breakdown

Added

No assets were added

Removed

No assets were removed

Bigger

Asset	File Size	% Changed
static/js/ReportRouter.js	1.5 MB → 1.5 MB (+209 B)	+0.01%

Smaller

Asset	File Size	% Changed
static/js/index.js	3.32 MB → 3.32 MB (-52 B)	-0.00%

Unchanged

Asset	File Size	% Changed
static/js/resize-observer.js	18.37 kB	0%
static/js/indexeddb-main-thread-worker-e59fee74.js	13.5 kB	0%
static/js/usePreviewTransactions.js	1.64 kB	0%
static/js/BackgroundImage.js	122.29 kB	0%
static/js/AppliedFilters.js	20.96 kB	0%
static/js/narrow.js	81.98 kB	0%
static/js/wide.js	225.26 kB	0%

[github-actions]

Bundle Stats — loot-core

Hey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle.

As this PR is updated, I'll keep you updated on how the bundle size is impacted.

Total

Files count	Total bundle size	% Changed
1	1.19 MB	0%

Changeset

No files were changed

View detailed bundle breakdown

Added

No assets were added

Removed

No assets were removed

Bigger

No assets were bigger

Smaller

No assets were smaller

Unchanged

Asset	File Size	% Changed
kcab.worker.js	1.19 MB	0%

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 365da79 and d2f3c51.

⛔ Files ignored due to path filters (1)

• upcoming-release-notes/3566.md is excluded by !**/*.md

📒 Files selected for processing (1)

• packages/desktop-client/src/components/reports/Overview.tsx (1 hunks)

🔇 Additional comments (1)

packages/desktop-client/src/components/reports/Overview.tsx (1)

85-104: Code logic for filtering baseLayout is correct

The updated code effectively filters the baseLayout array based on the isDashboardsFeatureEnabled flag and the presence of custom reports in customReportMap. This ensures that widgets are displayed appropriately depending on feature flags and available custom reports.