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

Handle duplicate categories/groups in nYNAB importer. #4293

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

youngcw
Copy link
Member

@youngcw youngcw commented Feb 4, 2025

Handles the condition where nYNAB imports have duplicate categories or groups.

fixes #3069

@actual-github-bot actual-github-bot bot changed the title Handle duplicate categories in nYNAB importer. [WIP] Handle duplicate categories in nYNAB importer. Feb 4, 2025
Copy link

netlify bot commented Feb 4, 2025

Deploy Preview for actualbudget ready!

Name Link
🔨 Latest commit 6feb7a8
🔍 Latest deploy log https://app.netlify.com/sites/actualbudget/deploys/67a3e86a5cb1ab00085cf7e3
😎 Deploy Preview https://deploy-preview-4293.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

github-actions bot commented Feb 4, 2025

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
16 6.79 MB → 6.79 MB (+101 B) +0.00%
Changeset
File Δ Size
node_modules/clsx/dist/clsx.js 🆕 +509 B 0 B → 509 B
node_modules/clsx/dist/clsx.js?commonjs-module 🆕 +27 B 0 B → 27 B
node_modules/react-grid-layout/build/ReactGridLayout.js 📉 -1 B (-0.00%) 24.96 kB → 24.96 kB
node_modules/react-grid-layout/build/GridItem.js 📉 -1 B (-0.00%) 21.49 kB → 21.49 kB
node_modules/react-grid-layout/build/components/WidthProvider.js 📉 -1 B (-0.02%) 5.22 kB → 5.22 kB
node_modules/clsx/dist/clsx.mjs 🔥 -368 B (-100%) 368 B → 0 B
node_modules/clsx/dist/clsx.mjs?commonjs-proxy 🔥 -64 B (-100%) 64 B → 0 B
View detailed bundle breakdown

Added

No assets were added

Removed

No assets were removed

Bigger

Asset File Size % Changed
static/js/index.js 4.29 MB → 4.29 MB (+168 B) +0.00%

Smaller

Asset File Size % Changed
static/js/ReportRouter.js 1.59 MB → 1.59 MB (-67 B) -0.00%

Unchanged

Asset File Size % Changed
static/js/workbox-window.prod.es5.js 5.69 kB 0%
static/js/en.js 99.34 kB 0%
static/js/AppliedFilters.js 10.52 kB 0%
static/js/indexeddb-main-thread-worker-e59fee74.js 13.5 kB 0%
static/js/useAccountPreviewTransactions.js 1.69 kB 0%
static/js/BackgroundImage.js 122.29 kB 0%
static/js/pt-BR.js 103.29 kB 0%
static/js/en-GB.js 99.33 kB 0%
static/js/resize-observer.js 18.37 kB 0%
static/js/de.js 78.37 kB 0%
static/js/narrow.js 84.94 kB 0%
static/js/uk.js 111.11 kB 0%
static/js/nl.js 83.87 kB 0%
static/js/wide.js 102.8 kB 0%

Copy link
Contributor

github-actions bot commented Feb 4, 2025

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.33 MB → 1.33 MB (+279 B) +0.02%
Changeset
File Δ Size
packages/loot-core/src/server/importers/ynab5.ts 📈 +1.49 kB (+9.09%) 16.36 kB → 17.84 kB
View detailed bundle breakdown

Added

No assets were added

Removed

No assets were removed

Bigger

Asset File Size % Changed
kcab.worker.js 1.33 MB → 1.33 MB (+279 B) +0.02%

Smaller

No assets were smaller

Unchanged

No assets were unchanged

@youngcw youngcw changed the title [WIP] Handle duplicate categories in nYNAB importer. Handle duplicate categories in nYNAB importer. Feb 4, 2025
Copy link
Contributor

coderabbitai bot commented Feb 4, 2025

Walkthrough

The changes introduce a retry mechanism in the importCategories function within the YNAB importer. The implementation allows the function to attempt creating a category or category group up to 10 times if the actual.createCategoryGroup or actual.createCategory functions fail. Each retry modifies the name by appending a counter to the original name. If the counter reaches 10 without success, an error is thrown. This change enhances error handling for transient errors or naming conflicts during the category creation process. No alterations were made to the declarations of exported or public entities.

Assessment against linked issues

Objective Addressed Explanation
Support multiple categories with duplicate names (#3069)

Suggested labels

:sparkles: Merged

Suggested reviewers

  • jfdoming

Tip

🌐 Web search-backed reviews and chat
  • We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
  • You can disable this feature by setting web_search: false in the knowledge_base settings.
  • Please share any feedback in the Discord discussion.

📜 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 0397b41 and 446edf6.

📒 Files selected for processing (1)
  • packages/loot-core/src/server/importers/ynab5.ts (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • packages/loot-core/src/server/importers/ynab5.ts
⏰ Context from checks skipped due to timeout of 90000ms (5)
  • GitHub Check: build (macos-latest)
  • GitHub Check: build (windows-latest)
  • GitHub Check: Analyze
  • GitHub Check: Wait for Netlify build to finish
  • GitHub Check: build (ubuntu-latest)

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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🧹 Nitpick comments (1)
packages/loot-core/src/server/importers/ynab5.ts (1)

115-135: Consider adding logging for renamed categories.

Adding debug logs when categories are renamed would help with troubleshooting import issues.

 while (run) {
   try {
     const id = await actual.createCategory({
       name: cat.name,
       group_id: groupId,
     });
     entityIdMap.set(cat.id, id);
     run = false;
   } catch (e) {
+    console.debug(`Retrying category creation with new name. Original: ${origName}, Attempt: ${count}`);
     cat.name = origName + '-' + count.toString();
     count += 1;
     if (count >= 100) {
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 0c1c8e6 and 774c01a.

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

packages/loot-core/src/server/importers/ynab5.ts Outdated Show resolved Hide resolved
@youngcw youngcw changed the title Handle duplicate categories in nYNAB importer. Handle duplicate categories/groups in nYNAB importer. Feb 4, 2025
@@ -79,13 +79,30 @@ async function importCategories(
if (
!equalsIgnoreCase(group.name, 'Internal Master Category') &&
!equalsIgnoreCase(group.name, 'Credit Card Payments') &&
!equalsIgnoreCase(group.name, 'Hidden Categories') &&
Copy link
Member Author

Choose a reason for hiding this comment

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

This group will be empty after the import, so just ignore it.

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]: nYNAB import fails due to duplicate category names because one is hidden
1 participant