Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix incorrect boldening of synced accounts in the sidebar #4009

Merged
merged 2 commits into from
Dec 19, 2024

Conversation

matt-fidd
Copy link
Contributor

Fixes #4008

@matt-fidd matt-fidd requested a review from youngcw December 18, 2024 21:52
@actual-github-bot actual-github-bot bot changed the title Fix incorrect boldening of synced accounts in the sidebar [WIP] Fix incorrect boldening of synced accounts in the sidebar Dec 18, 2024
@matt-fidd matt-fidd changed the title [WIP] Fix incorrect boldening of synced accounts in the sidebar Fix incorrect boldening of synced accounts in the sidebar Dec 18, 2024
Copy link

netlify bot commented Dec 18, 2024

Deploy Preview for actualbudget ready!

Name Link
🔨 Latest commit 877699d
🔍 Latest deploy log https://app.netlify.com/sites/actualbudget/deploys/67634436f65d5d0008a2ce98
😎 Deploy Preview https://deploy-preview-4009.demo.actualbudget.org
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

Copy link
Contributor

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
10 5.53 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
static/js/indexeddb-main-thread-worker-e59fee74.js 13.5 kB 0%
static/js/workbox-window.prod.es5.js 5.69 kB 0%
static/js/resize-observer.js 18.37 kB 0%
static/js/BackgroundImage.js 122.29 kB 0%
static/js/narrow.js 83.36 kB 0%
static/js/wide.js 161.25 kB 0%
static/js/useAccountPreviewTransactions.js 1.63 kB 0%
static/js/TransactionList.js 102.91 kB 0%
static/js/ReportRouter.js 1.58 MB 0%
static/js/index.js 3.45 MB 0%

Copy link
Contributor

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.32 MB → 1.32 MB (-14 B) -0.00%
Changeset
File Δ Size
packages/loot-core/src/server/main.ts 📉 -22 B (-0.03%) 64.92 kB → 64.9 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
kcab.worker.js 1.32 MB → 1.32 MB (-14 B) -0.00%

Unchanged

No assets were unchanged

Copy link
Contributor

coderabbitai bot commented Dec 18, 2024

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 eslint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

packages/loot-core/src/server/main.ts

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "eslint-plugin-eslint-plugin".

(The package "eslint-plugin-eslint-plugin" was not found when loaded as a Node module from the directory "/packages/eslint-plugin-actual".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-eslint-plugin@latest --save-dev

The plugin "eslint-plugin-eslint-plugin" was referenced from the config file in "packages/eslint-plugin-actual/.eslintrc.js".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.

Walkthrough

The pull request introduces modifications to the handleSyncResponse function in the packages/loot-core/src/server/main.ts file. The primary change simplifies the conditional logic for determining when to push an account ID to the updatedAccounts array. Previously, the condition checked both added.length and updated.length, but now it only checks added.length.

This modification potentially alters how account synchronization results are processed, specifically in how accounts are marked as updated during a sync operation. The error handling in the handleSyncError function remains unchanged, ensuring that specific error types continue to be processed correctly. The overall structure of the sync handlers is maintained, with no changes to their signatures or fundamental functionality.

Assessment against linked issues

Objective Addressed Explanation
Resolve incorrect account highlighting during sync [#4008] The change appears to modify sync logic, but it's unclear if this directly addresses the bolding issue described in the bug report
Prevent unnecessary account bolding during sync The simplified condition might impact how accounts are marked as updated, but the full impact is not immediately evident

Possibly related PRs

Suggested labels

sparkles: Merged

Suggested reviewers

  • youngcw
  • joel-jeremy

📜 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 11bde73 and 877699d.

⛔ Files ignored due to path filters (1)
  • upcoming-release-notes/4009.md is excluded by !**/*.md
📒 Files selected for processing (1)
  • packages/loot-core/src/server/main.ts (1 hunks)
🔇 Additional comments (1)
packages/loot-core/src/server/main.ts (1)

1059-1061: LGTM! The condition simplification aligns with UI expectations.

The change to only check added.length makes sense as it ensures accounts are only marked as "updated" when they have new transactions, not when existing transactions are modified. This aligns with typical UI patterns where bold styling indicates new/unread items.

Let's verify that no other UI components depend on updatedAccounts for updated transactions:

✅ Verification successful

LGTM! The change is safe and correctly fixes the account boldening behavior

The verification confirms that:

  1. The updatedAccounts array is only used for UI styling in the sidebar and mobile account views (packages/desktop-client/src/components/sidebar/Accounts.tsx and packages/desktop-client/src/components/mobile/accounts/Accounts.tsx)
  2. The change aligns with the PR objective to "Fix incorrect boldening of synced accounts in the sidebar" as mentioned in the release notes
  3. No other components depend on updatedAccounts for transaction updates, they only use it to determine if an account should be visually highlighted as having new transactions
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for UI components that might depend on updatedAccounts
rg -l "updatedAccounts" --type ts --type tsx

Length of output: 72


Script:

#!/bin/bash
# Search for updatedAccounts usage across all files
rg "updatedAccounts" -A 3 -B 3

Length of output: 21026


Script:

#!/bin/bash
# Find all TypeScript files that might reference updatedAccounts
fd ".*\.[jt]s$" | xargs rg "updatedAccounts"

Length of output: 2428


Script:

#!/bin/bash
# Search for UI components that might use the bold styling based on account updates
rg -A 3 "bold.*account|account.*bold" 

Length of output: 128


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
🪧 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.

Copy link
Member

@youngcw youngcw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome. Thanks!

@matt-fidd matt-fidd merged commit 6cfb9d2 into actualbudget:master Dec 19, 2024
20 checks passed
@matt-fidd matt-fidd deleted the sync-boldened branch December 19, 2024 15:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: Simplefin sync causes incorrect new transaction highlighting on some accounts
2 participants