✨ (dashboards) making "all widget" button always visible

[MatissJanis]

Feedback item here: #3282 (comment)

---

Before: "add widget" button was visible only in edit mode; "create custom report" button was visible only in non-edit mode

After: "add widget" button is always visible (both edit and non-edit mode); "create custom report" has been removed

---

These changes are under feature flag. Experience WITHOUT the feature flag has no changes (there is still a "create custom report" button)

[netlify]

✅ Deploy Preview for actualbudget ready!

Name	Link
🔨 Latest commit	a302539
🔍 Latest deploy log	https://app.netlify.com/sites/actualbudget/deploys/6702f055d0c75d00081aa03f
😎 Deploy Preview	https://deploy-preview-3588.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.3 MB → 5.29 MB (-218 B)	-0.00%

Changeset

File	Δ	Size
src/components/reports/Overview.tsx	📉 -218 B (-1.36%)	15.71 kB → 15.5 kB

View detailed bundle breakdown

Added

No assets were added

Removed

No assets were removed

Bigger

No assets were bigger

Smaller

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

Unchanged

Asset	File Size	% Changed
static/js/usePreviewTransactions.js	1.64 kB	0%
static/js/BackgroundImage.js	122.29 kB	0%
static/js/indexeddb-main-thread-worker-e59fee74.js	13.5 kB	0%
static/js/AppliedFilters.js	20.96 kB	0%
static/js/resize-observer.js	18.37 kB	0%
static/js/narrow.js	82.55 kB	0%
static/js/wide.js	225.26 kB	0%
static/js/index.js	3.32 MB	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]

Walkthrough

The pull request introduces changes to the Overview component within the Overview.tsx file. Key modifications include altering the conditions for rendering the "Add new widget" button, which now depends on the isDashboardsFeatureEnabled feature flag instead of the isEditing state. The logic for the "Finish editing dashboard" button has also been updated to show based on both the editing state and the feature flag. Additionally, the implementation for rendering buttons related to creating a new custom report and editing the dashboard has been simplified, ensuring that the editing button's display is contingent on the relevant feature being enabled. The invocation of the onAddWidget function remains unchanged but is now subject to the new conditional logic regarding feature flags and widget types. Overall, these changes streamline the user interface by ensuring that buttons are displayed only when applicable features are enabled, while the component's layout and structure remain consistent.

Possibly related PRs

• 🐛 (reports) deleting custom report should remove it from the dashboard #3469: The changes in this PR involve adding a feature flag check for the "dashboards" feature in the CustomReportListCards component, which is directly related to the modifications in the main PR that also focus on the isDashboardsFeatureEnabled feature flag for rendering buttons in the Overview component.

Suggested labels

<sparkles: Merged>

Suggested reviewers

• carkom

---

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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 38c5f89 and a302539.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

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

🧰 Additional context used

🔇 Additional comments (1)

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

Line range hint 344-427: Changes look good for the "Add new widget" button

The updated logic correctly ensures that the "Add new widget" button is always visible when the isDashboardsFeatureEnabled feature flag is enabled. This aligns with the PR objectives to improve the dashboard interface.