Skip to content

Workspace rate list display for auto-generated rates#96149

Open
thelullabyy wants to merge 4 commits into
Expensify:mainfrom
thelullabyy:fix/95280
Open

Workspace rate list display for auto-generated rates#96149
thelullabyy wants to merge 4 commits into
Expensify:mainfrom
thelullabyy:fix/95280

Conversation

@thelullabyy

@thelullabyy thelullabyy commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Fixed Issues

$ #95280
PROPOSAL: NA

Tests

Setup:

  • Open a paid workspace that has Distance rates enabled (Workspace > More features > toggle Distance rates if needed).
  • Go to Workspaces > [workspace] > Distance rates. Make sure at least 2 rates exist (add one via Add rate if needed) so you can compare a government rate against a normal one.

Seed a mock government rate:
With the Distance rates page open, turn off internet, run this in the browser console:

const policy = await window.policy;
const customUnit = Object.values(policy.customUnits).find((u) => u.name === 'Distance');
const rateID = Object.keys(customUnit.rates).at(0);
await window.Onyx.merge(`policy_${policy.id}`, {
    customUnits: {
        [customUnit.customUnitID]: {
            rates: {
                [rateID]: {
                    rate: 72.5,
                    startDate: '2026-01-01',
                    endDate: '2026-12-31',
                    attributes: {
                        governmentRate: {sourceRateID: 'US_2026-01-01', rate: 72.5, startDate: '2026-01-01', endDate: '2026-12-31'},
                    },
                },
            },
        },
    },
});

Verify that:

  1. Icon displays for an unmodified government rate

In the rates table, the seeded rate shows a small lightning-bolt icon next to the amount in the Rate column.
Hover the icon: tooltip reads "This rate is auto-generated."
Other rates show no icon.

  1. Narrow layout

Shrink the browser window to mobile width (or test on the mobile web layout).
The bolt icon appears next to the "rate • date" line under the rate name, with the same tooltip behavior on hover.

  1. Icon hides when the rate value is edited

Open the seeded rate > Rate, change the amount (e.g. 0.725 → 0.99), save.
Back in the list, the bolt icon is gone.

  1. Icon restores when the value is edited back

Change the amount back to exactly 0.725 and save.
The bolt icon reappears.

  1. Same hide/restore behavior for dates

Edit the Start date (e.g. to 2026-02-01) → icon hides. Restore to 2026-01-01 → icon returns.
Edit the End date (e.g. to 2026-11-30) → icon hides. Restore to 2026-12-31 → icon returns.

  1. Open-ended rate matching

Re-run the seed snippet but with endDate: null on the rate and no endDate key inside governmentRate → icon shows (omitted on both sides counts as a match).
Then set an end date on the rate via the UI → icon hides (omitted on only one side is not a match).

  1. Things that should NOT affect the icon

Rename the rate → icon stays (name isn't part of the snapshot).
Toggle the rate off/on via the switch → icon stays; only the status badge changes.
Sorting by any column and searching via Find rate work as before, with the icon following its row.

  1. Regression pass on a normal workspace

Open a workspace whose rates were never seeded: the list renders exactly as before, no icons, no layout shift in the Rate column.

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

Same as Tests

  • 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 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 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)
  • 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)
  • 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.
  • 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
Screen.Recording.2026-07-14.at.19.07.55.mov

@melvin-bot

melvin-bot Bot commented Jul 14, 2026

Copy link
Copy Markdown

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

  1. Look at the code and make sure there are no malicious changes.
  2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

@thelullabyy
thelullabyy marked this pull request as ready for review July 15, 2026 00:09
@thelullabyy
thelullabyy requested review from a team as code owners July 15, 2026 00:09
@melvin-bot
melvin-bot Bot requested review from cretadn22 and joekaufmanexpensify and removed request for a team July 15, 2026 00:09
@melvin-bot

melvin-bot Bot commented Jul 15, 2026

Copy link
Copy Markdown

@cretadn22 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 July 15, 2026 00:09
@thelullabyy

Copy link
Copy Markdown
Contributor Author

@neil-marcellini Could you please help trigger the translation workflow? Thanks

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5295e3c468

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/libs/PolicyDistanceRatesUtils.ts Outdated
@cretadn22

Copy link
Copy Markdown
Contributor

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 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 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)
  • 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)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately
    • 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
    • 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 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.
  • 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
Android: mWeb Chrome
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari

Comment thread src/libs/PolicyDistanceRatesUtils.ts Outdated
Comment thread src/libs/PolicyDistanceRatesUtils.ts Outdated
@cretadn22

Copy link
Copy Markdown
Contributor

@thelullabyy Mind taking a look at the failing typescript checks and Jest Unit Tests? Also, please upload the complete test videos when you get a chance

@thelullabyy

Copy link
Copy Markdown
Contributor Author

The test failed due to missing copies. I requested it here #96149 (comment)

@joekaufmanexpensify joekaufmanexpensify left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Good for product.

@thelullabyy

Copy link
Copy Markdown
Contributor Author

@neil-marcellini Please help run the translation workflow once you having time. Thanks

#96149 (comment)

@dylanexpensify

Copy link
Copy Markdown
Contributor

@thelullabyy done

@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 6b8c6f2eadb..4b3b0b74ec9 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -6993,6 +6993,7 @@ Der Control-Tarif beginnt bei 9 $ pro aktivem Mitglied und Monat.`,
             amountPerUnit: (unit: string) => `Betrag pro ${unit}`,
             startDate: 'Startdatum',
             endDate: 'Enddatum',
+            autoGeneratedRateTooltip: 'Dieser Satz wurde automatisch erzeugt.',
         },
         editor: {
             descriptionInputLabel: 'Beschreibung',
diff --git a/src/languages/es.ts b/src/languages/es.ts
index 9bf1359733e..520c9ea4001 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -6918,6 +6918,7 @@ El plan Controlar empieza en 9 $ por miembro activo al mes.`,
             amountPerUnit: (unit: string) => `Importe por ${unit}`,
             startDate: 'Fecha de inicio',
             endDate: 'Fecha de fin',
+            autoGeneratedRateTooltip: 'Esta tasa se genera automáticamente.',
         },
         editor: {
             nameInputLabel: 'Nombre',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 2f9ae12fa81..26e4b033992 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -7021,6 +7021,7 @@ Le forfait Control commence à 9 $ par Membre actif et par mois.`,
             amountPerUnit: (unit: string) => `Montant par ${unit}`,
             startDate: 'Date de début',
             endDate: 'Date de fin',
+            autoGeneratedRateTooltip: 'Ce taux est généré automatiquement.',
         },
         editor: {
             descriptionInputLabel: 'Description',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 6e49ff0d79c..8e8c686ac2d 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -6977,6 +6977,7 @@ Il piano Control parte da 9 $ al mese per ogni membro attivo.`,
             amountPerUnit: (unit: string) => `Importo per ${unit}`,
             startDate: 'Data di inizio',
             endDate: 'Data di fine',
+            autoGeneratedRateTooltip: 'Questa tariffa è generata automaticamente.',
         },
         editor: {
             descriptionInputLabel: 'Descrizione',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 2bde735c0fe..180bced4980 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -6894,6 +6894,7 @@ Control プランは、アクティブメンバー1人あたり月額 $9 から
             amountPerUnit: (unit: string) => `${unit}あたりの金額`,
             startDate: '開始日',
             endDate: '終了日',
+            autoGeneratedRateTooltip: 'このレートは自動生成されています。',
         },
         editor: {
             descriptionInputLabel: '説明',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 3bf61f9c238..b043b325edc 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -6960,6 +6960,7 @@ Het Control-abonnement begint bij $9 per actieve deelnemer per maand.`,
             amountPerUnit: (unit: string) => `Bedrag per ${unit}`,
             startDate: 'Startdatum',
             endDate: 'Einddatum',
+            autoGeneratedRateTooltip: 'Dit tarief is automatisch gegenereerd.',
         },
         editor: {
             descriptionInputLabel: 'Beschrijving',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index b4c34c53be2..5763693c374 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -6940,6 +6940,7 @@ Plan Control zaczyna się od 9 USD za aktywnego członka miesięcznie.`,
             amountPerUnit: (unit: string) => `Kwota za ${unit}`,
             startDate: 'Data rozpoczęcia',
             endDate: 'Data zakończenia',
+            autoGeneratedRateTooltip: 'Ta stawka jest generowana automatycznie.',
         },
         editor: {
             descriptionInputLabel: 'Opis',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 429816f1f13..9a1b617fabc 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -6952,6 +6952,7 @@ O plano Control começa em US$ 9 por membro ativo por mês.`,
             amountPerUnit: (unit: string) => `Valor por ${unit}`,
             startDate: 'Data de início',
             endDate: 'Data de término',
+            autoGeneratedRateTooltip: 'Essa tarifa é gerada automaticamente.',
         },
         editor: {
             descriptionInputLabel: 'Descrição',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 286066528d3..4b9289c9cd9 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -6758,6 +6758,7 @@ _如需更详细的说明,请[访问我们的帮助网站](${CONST.NETSUITE_IM
             amountPerUnit: (unit: string) => `每${unit}金额`,
             startDate: '开始日期',
             endDate: '结束日期',
+            autoGeneratedRateTooltip: '此费率为自动生成。',
         },
         editor: {
             descriptionInputLabel: '描述',

Note

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

View workflow run

@cretadn22

Copy link
Copy Markdown
Contributor

@thelullabyy Could you please update the translations and resolve my earlier comments?

@codecov

codecov Bot commented Jul 19, 2026

Copy link
Copy Markdown

Codecov Report

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

Files with missing lines Coverage Δ
src/CONST/index.ts 94.81% <ø> (ø)
src/libs/PolicyDistanceRatesUtils.ts 16.92% <100.00%> (+8.44%) ⬆️
...ce/distanceRates/PolicyDistanceRateDetailsPage.tsx 0.00% <0.00%> (ø)
...tanceRatesTable/WorkspaceDistanceRatesTableRow.tsx 0.00% <0.00%> (ø)
... and 10 files with indirect coverage changes

@thelullabyy

Copy link
Copy Markdown
Contributor Author

@cretadn22 resolved the code issues. For the recordings, I will re-upload soon...

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