Fix goals tooltip translation

[youngcw]

Looks like adding in a context flag modifies the base key, which we cant do since the key is what gets used for English text.

To test, add a #goal to a category and look at the tooltip after running templates. On edge it will say "Long_noun" on the PR it will just say "Long". You will need to be on English and not "British English" language.

[netlify]

✅ Deploy Preview for actualbudget ready!

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

[coderabbitai]

Walkthrough

This pull request updates the tooltip content in the BalanceWithCarryover component. The change modifies the translation call used for displaying the type "Long" in the tooltip when the longGoalValue equals 1. Previously, the translation function was called with an extra context parameter as t('Long', { context: 'noun' }). The update simplifies this by calling t('Long') instead. No other modifications, including changes to component props or public interfaces, have been made.

Suggested labels

:sparkles: Merged

Suggested reviewers

• youngcw

---

📜 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 e86cbcd and b694eb9.

📒 Files selected for processing (1)

• packages/desktop-client/src/components/budget/BalanceWithCarryover.tsx (1 hunks)

🔇 Additional comments (1)

packages/desktop-client/src/components/budget/BalanceWithCarryover.tsx (1)

190-190:

✅ Verification successful

LGTM! Translation fix looks correct.

The removal of the context parameter from the translation call aligns with the PR objectives and should fix the tooltip displaying "Long_noun" instead of "Long".

Let's verify the translation behavior:

---

🏁 Script executed:

#!/bin/bash
# Description: Search for other instances of 'Long' translations to ensure consistency

# Test: Search for other translation calls with 'Long'
rg "t\(['\"](Long|long)['\"]" --type ts --type tsx

Length of output: 84

---

Please run this updated script to verify that there are no unexpected occurrences of the translation call with "Long" outside of the intended change. Once confirmed, the change in packages/desktop-client/src/components/budget/BalanceWithCarryover.tsx (line 190) can be considered correctly isolated.

Action: Re-run the above script for manual verification of translation consistency.

---

🏁 Script executed:

[run_scripts]
#!/bin/bash
# Searching for translation calls of "Long" (and "long") in TypeScript and TSX files
echo "Searching in TS files:"
rg "t\(['\"](Long|long)['\"]" -g "*.ts" .
echo "Searching in TSX files:"
rg "t\(['\"](Long|long)['\"]" -g "*.tsx" .

Length of output: 330

---

Translation fix verified – Approved

The change in packages/desktop-client/src/components/budget/BalanceWithCarryover.tsx (line 190) successfully removes the unwanted context parameter from the translation call, which should prevent the tooltip from displaying "Long_noun". Automated searches for other occurrences of t('Long') (and t('long')) in both TS and TSX files returned no additional matches, which indicates that this change is properly isolated.

Please perform manual verification to ensure no unintended translation references remain.

---

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

[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
17	6.93 MB → 6.93 MB (-71 B)	-0.00%

Changeset

File	Δ	Size
src/components/budget/BalanceWithCarryover.tsx	📉 -71 B (-0.96%)	7.21 kB → 7.14 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/index.js	4.31 MB → 4.31 MB (-71 B)	-0.00%

Unchanged

Asset	File Size	% Changed
static/js/workbox-window.prod.es5.js	5.69 kB	0%
static/js/fr.js	71.59 kB	0%
static/js/resize-observer.js	18.37 kB	0%
static/js/indexeddb-main-thread-worker-e59fee74.js	13.5 kB	0%
static/js/en-GB.js	99.42 kB	0%
static/js/nl.js	98.54 kB	0%
static/js/en.js	100.54 kB	0%
static/js/useAccountPreviewTransactions.js	1.69 kB	0%
static/js/narrow.js	85.57 kB	0%
static/js/uk.js	111.11 kB	0%
static/js/BackgroundImage.js	122.29 kB	0%
static/js/de.js	111.72 kB	0%
static/js/wide.js	102.8 kB	0%
static/js/AppliedFilters.js	10.52 kB	0%
static/js/pt-BR.js	106.43 kB	0%
static/js/ReportRouter.js	1.59 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.33 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.33 MB	0%

[matt-fidd]

@jfdoming FYI

[jfdoming]

Interesting. Feel like we could probably support context explicitly for English, but this fix makes sense for now