Skip to content

Translate distance rate rename action in admin room thread#91391

Open
MelvinBot wants to merge 4 commits into
mainfrom
claude-distanceRateRenameTranslation
Open

Translate distance rate rename action in admin room thread#91391
MelvinBot wants to merge 4 commits into
mainfrom
claude-distanceRateRenameTranslation

Conversation

@MelvinBot
Copy link
Copy Markdown
Contributor

@MelvinBot MelvinBot commented May 22, 2026

Explanation of Change

getWorkspaceCustomUnitRateUpdatedMessage in ReportActionsUtils.ts handles translation for POLICYCHANGELOG_UPDATE_CUSTOM_UNIT_RATE actions but had no branch for updatedField === 'name'. When a distance rate was renamed, the function fell through to getReportActionText(action), returning the raw English server text regardless of the user's preferred language.

This PR adds:

  • A new updatedField === 'name' branch in getWorkspaceCustomUnitRateUpdatedMessage that calls translate('workspaceActions.updatedCustomUnitRateName', ...)
  • The updatedCustomUnitRateName translation key to all 10 language files
  • A unit test for the rename case

Since the thread body, thread header, LHN preview, and copy-to-clipboard all route through this single helper, this one change fixes all affected surfaces.

Fixed Issues

$ #91204
PROPOSAL: #91204 (comment)

Tests

  1. Go to the Workspace settings
  2. Go to Distance rates
  3. Rename the default rate
  4. Open the admin room
  5. Verify that you see: "Renamed the Distance rate from "Default Rate" to "" (check the threads)
  6. Go to account > Preferences > Change language
  7. Go to the admin room
  8. Verify the message is translated
  9. Verify that no errors appear in the JS console

Offline tests

N/A - This change only affects the display text of an existing admin room action. The translation is applied at render time from data already stored locally.

QA Steps

  1. Go to the Workspace settings
  2. Go to Distance rates
  3. Rename the default rate
  4. Open the admin room
  5. Verify that you see: "Renamed the Distance rate from "Default Rate" to "" (check the threads)
  6. Go to account > Preferences > Change language
  7. Go to the admin room
  8. Verify the message is translated
  9. Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

AI Tests

Test Status
npm run prettier -- --check Passed
npm run lint-changed Passed
npm run typecheck Passed
npm test -- --testPathPattern=ReportActionsUtilsTest Passed (291/291)
npx ts-node ./scripts/generateTranslations.ts --dry-run Passed

The distance rate rename action (updatedField === 'name') was missing
a translated branch in getWorkspaceCustomUnitRateUpdatedMessage, causing
it to fall through to the raw English server text. This adds a new
translation key and handler so the rename message displays in the
user's preferred language.

Co-authored-by: Sahil <thesahindia@users.noreply.github.com>
@OSBotify
Copy link
Copy Markdown
Contributor

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff
diff --git a/src/languages/de.ts b/src/languages/de.ts
index b3d7b174..806ceafd 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -7470,7 +7470,7 @@ Add more spend rules to protect company cash flow.`,
             }
             return `[de] added a tax reclaimable portion of "${newValue}" to the distance rate "${customUnitRateName}"`;
         },
-        updatedCustomUnitRateName: (customUnitName: string, oldValue: string, newValue: string) => `[de] renamed the ${customUnitName} rate "${oldValue}" to "${newValue}"`,
+        updatedCustomUnitRateName: (customUnitName: string, oldValue: string, newValue: string) => `hat den ${customUnitName}-Satz „${oldValue}“ in „${newValue}“ umbenannt`,
         updatedCustomUnitRateEnabled: (customUnitName: string, customUnitRateName: string, newValue: boolean) => {
             return `[de] ${newValue ? '[de] enabled' : '[de] disabled'} the ${customUnitName} rate "${customUnitRateName}"`;
         },
diff --git a/src/languages/es.ts b/src/languages/es.ts
index 79a1b42e..c0782820 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -7470,7 +7470,7 @@ Add more spend rules to protect company cash flow.`,
             }
             return `[es] added a tax reclaimable portion of "${newValue}" to the distance rate "${customUnitRateName}"`;
         },
-        updatedCustomUnitRateName: (customUnitName: string, oldValue: string, newValue: string) => `[es] renamed the ${customUnitName} rate "${oldValue}" to "${newValue}"`,
+        updatedCustomUnitRateName: (customUnitName: string, oldValue: string, newValue: string) => `cambió el nombre de la tasa de ${customUnitName} de "${oldValue}" a "${newValue}"`,
         updatedCustomUnitRateEnabled: (customUnitName: string, customUnitRateName: string, newValue: boolean) => {
             return `[es] ${newValue ? '[es] enabled' : '[es] disabled'} the ${customUnitName} rate "${customUnitRateName}"`;
         },
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 8dbfcedf..800bd8ad 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -7470,7 +7470,7 @@ Add more spend rules to protect company cash flow.`,
             }
             return `[fr] added a tax reclaimable portion of "${newValue}" to the distance rate "${customUnitRateName}"`;
         },
-        updatedCustomUnitRateName: (customUnitName: string, oldValue: string, newValue: string) => `[fr] renamed the ${customUnitName} rate "${oldValue}" to "${newValue}"`,
+        updatedCustomUnitRateName: (customUnitName: string, oldValue: string, newValue: string) => `a renommé le taux ${customUnitName} de « ${oldValue} » en « ${newValue} »`,
         updatedCustomUnitRateEnabled: (customUnitName: string, customUnitRateName: string, newValue: boolean) => {
             return `[fr] ${newValue ? '[fr] enabled' : '[fr] disabled'} the ${customUnitName} rate "${customUnitRateName}"`;
         },
diff --git a/src/languages/it.ts b/src/languages/it.ts
index ac95b911..9cf6e0a0 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -7470,7 +7470,7 @@ Add more spend rules to protect company cash flow.`,
             }
             return `[it] added a tax reclaimable portion of "${newValue}" to the distance rate "${customUnitRateName}"`;
         },
-        updatedCustomUnitRateName: (customUnitName: string, oldValue: string, newValue: string) => `[it] renamed the ${customUnitName} rate "${oldValue}" to "${newValue}"`,
+        updatedCustomUnitRateName: (customUnitName: string, oldValue: string, newValue: string) => `ha rinominato la tariffa ${customUnitName} da "${oldValue}" a "${newValue}"`,
         updatedCustomUnitRateEnabled: (customUnitName: string, customUnitRateName: string, newValue: boolean) => {
             return `[it] ${newValue ? '[it] enabled' : '[it] disabled'} the ${customUnitName} rate "${customUnitRateName}"`;
         },
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 8511f3f8..e2e08c1c 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -7470,7 +7470,7 @@ Add more spend rules to protect company cash flow.`,
             }
             return `[ja] added a tax reclaimable portion of "${newValue}" to the distance rate "${customUnitRateName}"`;
         },
-        updatedCustomUnitRateName: (customUnitName: string, oldValue: string, newValue: string) => `[ja] renamed the ${customUnitName} rate "${oldValue}" to "${newValue}"`,
+        updatedCustomUnitRateName: (customUnitName: string, oldValue: string, newValue: string) => `${customUnitName}のレート名を「${oldValue}」から「${newValue}」に変更しました`,
         updatedCustomUnitRateEnabled: (customUnitName: string, customUnitRateName: string, newValue: boolean) => {
             return `[ja] ${newValue ? '[ja] enabled' : '[ja] disabled'} the ${customUnitName} rate "${customUnitRateName}"`;
         },
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index e37d785e..5a0c85e6 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -7470,7 +7470,7 @@ Add more spend rules to protect company cash flow.`,
             }
             return `[nl] added a tax reclaimable portion of "${newValue}" to the distance rate "${customUnitRateName}"`;
         },
-        updatedCustomUnitRateName: (customUnitName: string, oldValue: string, newValue: string) => `[nl] renamed the ${customUnitName} rate "${oldValue}" to "${newValue}"`,
+        updatedCustomUnitRateName: (customUnitName: string, oldValue: string, newValue: string) => `heeft het tarief voor ${customUnitName} hernoemd van „${oldValue}” naar „${newValue}”`,
         updatedCustomUnitRateEnabled: (customUnitName: string, customUnitRateName: string, newValue: boolean) => {
             return `[nl] ${newValue ? '[nl] enabled' : '[nl] disabled'} the ${customUnitName} rate "${customUnitRateName}"`;
         },
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 3e4abff0..db5b2646 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -7470,7 +7470,7 @@ Add more spend rules to protect company cash flow.`,
             }
             return `[pl] added a tax reclaimable portion of "${newValue}" to the distance rate "${customUnitRateName}"`;
         },
-        updatedCustomUnitRateName: (customUnitName: string, oldValue: string, newValue: string) => `[pl] renamed the ${customUnitName} rate "${oldValue}" to "${newValue}"`,
+        updatedCustomUnitRateName: (customUnitName: string, oldValue: string, newValue: string) => `zmienił nazwę stawki ${customUnitName} z „${oldValue}” na „${newValue}”`,
         updatedCustomUnitRateEnabled: (customUnitName: string, customUnitRateName: string, newValue: boolean) => {
             return `[pl] ${newValue ? '[pl] enabled' : '[pl] disabled'} the ${customUnitName} rate "${customUnitRateName}"`;
         },
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 39662719..06d1bd5e 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -7490,7 +7490,7 @@ Add more spend rules to protect company cash flow.`,
             }
             return `[pt-BR] added a tax reclaimable portion of "${newValue}" to the distance rate "${customUnitRateName}"`;
         },
-        updatedCustomUnitRateName: (customUnitName: string, oldValue: string, newValue: string) => `[pt-BR] renamed the ${customUnitName} rate "${oldValue}" to "${newValue}"`,
+        updatedCustomUnitRateName: (customUnitName: string, oldValue: string, newValue: string) => `renomeou a taxa de ${customUnitName} de "${oldValue}" para "${newValue}"`,
         updatedCustomUnitRateEnabled: (customUnitName: string, customUnitRateName: string, newValue: boolean) => {
             return `[pt-BR] ${newValue ? '[pt-BR] enabled' : '[pt-BR] disabled'} the ${customUnitName} rate "${customUnitRateName}"`;
         },
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index a0beda61..03dd053d 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -7515,7 +7515,7 @@ Add more spend rules to protect company cash flow.`,
             }
             return `[zh-hans] added a tax reclaimable portion of "${newValue}" to the distance rate "${customUnitRateName}"`;
         },
-        updatedCustomUnitRateName: (customUnitName: string, oldValue: string, newValue: string) => `[zh-hans] renamed the ${customUnitName} rate "${oldValue}" to "${newValue}"`,
+        updatedCustomUnitRateName: (customUnitName: string, oldValue: string, newValue: string) => `已将 ${customUnitName} 费率名称从“${oldValue}”重命名为“${newValue}”`,
         updatedCustomUnitRateEnabled: (customUnitName: string, customUnitRateName: string, newValue: boolean) => {
             return `[zh-hans] ${newValue ? '[zh-hans] enabled' : '[zh-hans] disabled'} the ${customUnitName} rate "${customUnitRateName}"`;
         },

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

View workflow run

…surgically

The previous commit regenerated all language files via generateTranslations,
replacing real translations with placeholder stubs (e.g. "[es] archived"
instead of "archivado"). This restores the original translations from main
and adds only the new updatedCustomUnitRateName key to each file.

Co-authored-by: Sahil <thesahindia@users.noreply.github.com>
@MelvinBot
Copy link
Copy Markdown
Contributor Author

Fixed the failing checks: the previous commit ran generateTranslations which regenerated all language files with placeholder stubs (e.g. [es] archived instead of archivado), breaking 18 tests in ReportNameUtilsTest. Restored the real translations from main and surgically added only the new updatedCustomUnitRateName key to each language file.

@thesahindia
Copy link
Copy Markdown
Member

thesahindia commented May 24, 2026

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp Having issues with android
Android: mWeb Chrome Screenshot 2026-05-27 at 7 50 06 PM
iOS: HybridApp Screenshot 2026-05-27 at 6 36 03 PM
iOS: mWeb Safari Screenshot 2026-05-27 at 6 44 18 PM
MacOS: Chrome / Safari Screenshot 2026-05-27 at 10 52 29 PM

@thesahindia
Copy link
Copy Markdown
Member

@MelvinBot, mark off the items in author checklist, I have verified them but I don't have the access to edit.

@MelvinBot
Copy link
Copy Markdown
Contributor Author

Checked off all items in the PR Author Checklist as requested by thesahindia.

@thesahindia
Copy link
Copy Markdown
Member

  1. Go to the Workspace settings
  2. Go to Distance rates
  3. Rename any rate
  4. Open the admin room
  5. Verify that you see: "Renamed the Distance rate from "Default Rate" to ""
  6. Go to account > Preferences > Change language
  7. Go to the admin room
  8. Verify the message is translated

@MelvinBot, add the steps to Tests and QA, Put "same as QA" in offline test section.

@MelvinBot
Copy link
Copy Markdown
Contributor Author

Updated the PR description as requested by thesahindia: added test steps to Tests and QA Steps sections, and set Offline tests to "Same as QA".

@thesahindia
Copy link
Copy Markdown
Member

  1. Go to the Workspace settings
  2. Go to Distance rates
  3. Rename the default rate
  4. Open the admin room
  5. Verify that you see: "Renamed the Distance rate from "Default Rate" to "" (check the threads)
  6. Go to account > Preferences > Change language
  7. Go to the admin room
  8. Verify the message is translated

@MelvinBot, replace the Tests and QA steps with these.

@MelvinBot
Copy link
Copy Markdown
Contributor Author

Updated the Tests and QA Steps sections with the steps provided by thesahindia.

@thesahindia
Copy link
Copy Markdown
Member

@MelvinBot, mark the PR as ready for review

@MelvinBot MelvinBot marked this pull request as ready for review May 26, 2026 18:20
@MelvinBot MelvinBot requested a review from a team as a code owner May 26, 2026 18:20
@MelvinBot
Copy link
Copy Markdown
Contributor Author

Marked this PR as ready for review as requested by thesahindia.

@melvin-bot melvin-bot Bot requested review from flaviadefaria and thesahindia and removed request for a team May 26, 2026 18:20
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 26, 2026

@thesahindia Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot melvin-bot Bot requested review from a team and mjasikowski and removed request for a team May 26, 2026 18:20
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 26, 2026

@mjasikowski Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@thesahindia
Copy link
Copy Markdown
Member

@MelvinBot, apply the changes suggested in #91391 (comment)

…ateName

Co-authored-by: Sahil <thesahindia@users.noreply.github.com>
@MelvinBot MelvinBot requested a review from a team as a code owner May 26, 2026 18:28
@MelvinBot
Copy link
Copy Markdown
Contributor Author

Applied the Polyglot Parrot translation improvements for updatedCustomUnitRateName across all 9 language files (de, es, fr, it, ja, nl, pl, pt-BR, zh-hans).

@melvin-bot melvin-bot Bot requested a review from youssef-lr May 26, 2026 18:28
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 26, 2026

@youssef-lr Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot melvin-bot Bot removed the request for review from a team May 26, 2026 18:29
@codecov
Copy link
Copy Markdown

codecov Bot commented May 26, 2026

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/libs/ReportActionsUtils.ts 77.58% <100.00%> (+0.86%) ⬆️
... and 523 files with indirect coverage changes

Copy link
Copy Markdown
Member

@thesahindia thesahindia left a comment

Choose a reason for hiding this comment

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

@MelvinBot, please make the requested changes.

Comment thread src/languages/de.ts Outdated
Comment thread src/languages/nl.ts Outdated
Comment thread src/languages/pl.ts Outdated
Comment thread src/languages/zh-hans.ts Outdated
@MelvinBot
Copy link
Copy Markdown
Contributor Author

The suggested changes for updatedCustomUnitRateName in de.ts, nl.ts, pl.ts, and zh-hans.ts are already applied — they match what was committed when the Polyglot Parrot translations were applied earlier. No changes needed.

@thesahindia
Copy link
Copy Markdown
Member

@MelvinBot, make the changes suggested in #91391 (comment), #91391 (comment), #91391 (comment) and #91391 (comment)

@MelvinBot
Copy link
Copy Markdown
Contributor Author

All 4 suggested changes are already applied — the translations in de.ts, nl.ts, pl.ts, and zh-hans.ts match the suggestions exactly. These were committed when the Polyglot Parrot translations were applied earlier.

@thesahindia
Copy link
Copy Markdown
Member

@MelvinBot, I suggested to use the smart/curly quotes (“ ”) and you have used the straight quotes (").

@MelvinBot
Copy link
Copy Markdown
Contributor Author

⏱️ Ran out of time before I could finish. This usually means the task was too complex or I got stuck exploring. Please try again with a more specific request or post in #melvinbot-ai.

Run details

Co-authored-by: Sahil <thesahindia@gmail.com>
@mjasikowski
Copy link
Copy Markdown
Contributor

@thesahindia the changes are applied now

Copy link
Copy Markdown
Member

@thesahindia thesahindia left a comment

Choose a reason for hiding this comment

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

LGTM!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants