Skip to content

Make IOURequestStepPerDiemWorkspace use new SelectionList#71976

Merged
grgia merged 3 commits intoExpensify:mainfrom
software-mansion-labs:@GCyganek/migrate-IOURequestStepPerDiemWorkspace-SelectionList
Oct 14, 2025
Merged

Make IOURequestStepPerDiemWorkspace use new SelectionList#71976
grgia merged 3 commits intoExpensify:mainfrom
software-mansion-labs:@GCyganek/migrate-IOURequestStepPerDiemWorkspace-SelectionList

Conversation

@GCyganek
Copy link
Copy Markdown
Contributor

@GCyganek GCyganek commented Oct 7, 2025

Explanation of Change

Fixed Issues

$ #65655
PROPOSAL: N/A

Tests

  1. Create at least two workspaces with enabled Per diem feature
  2. Upload per diem rates spreadsheets for at least two workspaces:
Screen.Recording.2025-10-07.at.11.57.26.mov
  1. Use Create expanse to open the Right Hand Panel and click on the Per diem tab to open the list
  2. Verify that the list is working correctly
  • 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
    • MacOS: Desktop
  • 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 verified there are no new alerts related to the canBeMissing param for useOnyx
  • 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
Screen.Recording.2025-10-07.at.12.12.23.mov
Android: mWeb Chrome
Screen.Recording.2025-10-07.at.12.09.41.mov
iOS: Native
Screen.Recording.2025-10-07.at.12.16.08.mov
iOS: mWeb Safari
Screen.Recording.2025-10-07.at.12.17.12.mov
MacOS: Chrome / Safari
Screen.Recording.2025-10-07.at.11.52.32.mov
MacOS: Desktop
Screen.Recording.2025-10-07.at.12.07.21.mov

@codecov
Copy link
Copy Markdown

codecov bot commented Oct 7, 2025

Codecov Report

❌ Patch coverage is 1.92308% with 51 lines in your changes missing coverage. Please review.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #71976      +/-   ##
==========================================
- Coverage   35.22%   35.19%   -0.03%     
==========================================
  Files        3290     3298       +8     
  Lines      107480   108205     +725     
  Branches    34291    34591     +300     
==========================================
+ Hits        37855    38078     +223     
- Misses      69440    69941     +501     
- Partials      185      186       +1     

📢 Thoughts on this report? Let us know!

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@GCyganek GCyganek changed the title Make IOURequestStepPerDiemWorkspace use new SelectionList Make IOURequestStepPerDiemWorkspace use new SelectionList Oct 7, 2025
Copy link
Copy Markdown
Contributor

@blazejkustra blazejkustra left a comment

Choose a reason for hiding this comment

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

LGTM

@GCyganek GCyganek marked this pull request as ready for review October 7, 2025 11:51
@GCyganek GCyganek requested a review from a team as a code owner October 7, 2025 11:51
@melvin-bot melvin-bot bot requested review from rushatgabhane and removed request for a team October 7, 2025 11:51
@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Oct 7, 2025

@rushatgabhane 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]

@GCyganek
Copy link
Copy Markdown
Contributor Author

GCyganek commented Oct 7, 2025

@Expensify/design

FYI, same as here, I'm getting rid of the Workspaces label

With label:
Screenshot 2025-10-07 at 11 48 19

Without it:

Screenshot 2025-10-07 at 11 48 25

Let me know if I should keep it instead

@shawnborton
Copy link
Copy Markdown
Contributor

Let me know if I should keep it instead

In this particular case, I think it would be beneficial to actually say "Choose a workspace" as the label - otherwise it feels a little blunt to just have a list of workspaces as the first thing you see. Thoughts @Expensify/design ?

@dannymcclain
Copy link
Copy Markdown
Contributor

Oh yes totally agree for this situation.

@dubielzyk-expensify
Copy link
Copy Markdown
Contributor

Agree. I remember having the thought of removing it back in the day, but Danny rightfully pointed out that it helps for the reasons Shawn mentions 👍

@GCyganek
Copy link
Copy Markdown
Contributor Author

GCyganek commented Oct 8, 2025

Thanks, I will add Choose a workspace label after I get confirmation for Spanish translation 👀

@GCyganek GCyganek requested a review from blazejkustra October 8, 2025 09:25
@GCyganek
Copy link
Copy Markdown
Contributor Author

GCyganek commented Oct 8, 2025

Ready
Screenshot 2025-10-08 at 11 37 55

Adding translations for the label for other languages...

@shawnborton
Copy link
Copy Markdown
Contributor

Works for me, thanks!

@OSBotify
Copy link
Copy Markdown
Contributor

OSBotify commented Oct 8, 2025

🦜 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 8a3b4e92..e6c34f7c 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -659,7 +659,7 @@ const translations = {
         reschedule: 'Verschieben',
         general: 'Allgemein',
         workspacesTabTitle: 'Arbeitsbereiche',
-        getTheApp: 'Hole dir die App',
+        getTheApp: 'Hol dir die App',
         scanReceiptsOnTheGo: 'Scannen Sie Belege von Ihrem Telefon aus',
         headsUp: 'Achtung!',
         submitTo: 'Einreichen an',
@@ -1047,11 +1047,11 @@ const translations = {
         upload: 'Beleg hochladen',
         uploadMultiple: 'Belege hochladen',
         dragReceiptBeforeEmail: 'Ziehen Sie eine Quittung auf diese Seite oder leiten Sie eine Quittung weiter an',
-        dragReceiptsBeforeEmail: 'Ziehen Sie Quittungen auf diese Seite oder leiten Sie Quittungen weiter an',
+        dragReceiptsBeforeEmail: 'Ziehen Sie Belege auf diese Seite oder leiten Sie Belege weiter an',
         dragReceiptAfterEmail: 'oder wählen Sie unten eine Datei zum Hochladen aus.',
         dragReceiptsAfterEmail: 'oder wählen Sie unten Dateien zum Hochladen aus.',
-        chooseReceipt: 'Wählen Sie eine Quittung zum Hochladen aus oder leiten Sie eine Quittung weiter an',
-        chooseReceipts: 'Wählen Sie Quittungen zum Hochladen aus oder leiten Sie Quittungen weiter an ',
+        chooseReceipt: 'Wählen Sie einen Beleg zum Hochladen aus oder leiten Sie einen Beleg weiter an',
+        chooseReceipts: 'Wählen Sie Belege zum Hochladen aus oder leiten Sie Belege weiter an',
         takePhoto: 'Ein Foto machen',
         cameraAccess: 'Der Kamerazugriff ist erforderlich, um Fotos von Belegen zu machen.',
         deniedCameraAccess: 'Kamerazugriff wurde noch nicht gewährt, bitte folgen Sie',
@@ -1466,6 +1466,7 @@ const translations = {
                 subtitle: 'Wählen Sie einen zusätzlichen Genehmiger für diesen Bericht, bevor wir ihn durch den Rest des Genehmigungs-Workflows leiten.',
             },
         },
+        chooseWorkspace: 'Wählen Sie einen Arbeitsbereich aus',
     },
     transactionMerge: {
         listPage: {
@@ -4810,7 +4811,7 @@ const translations = {
             textAlternateText: 'Fügen Sie ein Feld für die freie Texteingabe hinzu.',
             dateAlternateText: 'Fügen Sie einen Kalender zur Datumauswahl hinzu.',
             dropdownAlternateText: 'Fügen Sie eine Liste von Optionen zur Auswahl hinzu.',
-            formulaAlternateText: 'Fügen Sie ein Formularfeld hinzu.',
+            formulaAlternateText: 'Ein Formularfeld hinzufügen.',
             nameInputSubtitle: 'Wählen Sie einen Namen für das Berichtsfeld.',
             typeInputSubtitle: 'Wählen Sie aus, welche Art von Berichtsfeld verwendet werden soll.',
             initialValueInputSubtitle: 'Geben Sie einen Startwert ein, der im Berichtsfeld angezeigt werden soll.',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 9aa0ba3a..8186981d 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -1045,7 +1045,7 @@ const translations = {
         upload: 'Télécharger le reçu',
         uploadMultiple: 'Télécharger des reçus',
         dragReceiptBeforeEmail: 'Faites glisser un reçu sur cette page, transférez un reçu à',
-        dragReceiptsBeforeEmail: 'Faites glisser des reçus sur cette page, transférez des reçus à',
+        dragReceiptsBeforeEmail: 'Faites glisser les reçus sur cette page, transférez les reçus à',
         dragReceiptAfterEmail: 'ou choisissez un fichier à télécharger ci-dessous.',
         dragReceiptsAfterEmail: 'ou choisissez des fichiers à télécharger ci-dessous.',
         chooseReceipt: 'Choisissez un reçu à télécharger ou transférez un reçu à',
@@ -1465,6 +1465,7 @@ const translations = {
                 subtitle: "Choisissez un approbateur supplémentaire pour ce rapport avant de le faire passer par le reste du flux de travail d'approbation.",
             },
         },
+        chooseWorkspace: 'Choisissez un espace de travail',
     },
     transactionMerge: {
         listPage: {
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 66380497..c70f4c9b 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -1041,11 +1041,11 @@ const translations = {
         upload: 'Carica ricevuta',
         uploadMultiple: 'Carica ricevute',
         dragReceiptBeforeEmail: 'Trascina una ricevuta su questa pagina, inoltra una ricevuta a',
-        dragReceiptsBeforeEmail: 'Trascina ricevute su questa pagina, inoltra ricevute a',
-        dragReceiptAfterEmail: 'oppure scegli un file da caricare qui sotto.',
-        dragReceiptsAfterEmail: 'oppure scegli file da caricare qui sotto.',
+        dragReceiptsBeforeEmail: 'Trascina le ricevute su questa pagina, inoltra le ricevute a',
+        dragReceiptAfterEmail: 'o scegli un file da caricare qui sotto.',
+        dragReceiptsAfterEmail: 'oppure scegli i file da caricare qui sotto.',
         chooseReceipt: 'Scegli una ricevuta da caricare o inoltra una ricevuta a',
-        chooseReceipts: 'Scegli ricevute da caricare o inoltra ricevute a',
+        chooseReceipts: 'Scegli le ricevute da caricare o inoltra le ricevute a',
         takePhoto: 'Scatta una foto',
         cameraAccess: "L'accesso alla fotocamera è necessario per scattare foto delle ricevute.",
         deniedCameraAccess: "L'accesso alla fotocamera non è ancora stato concesso, si prega di seguire",
@@ -1459,6 +1459,7 @@ const translations = {
                 subtitle: 'Scegli un approvatore aggiuntivo per questo report prima di instradarlo attraverso il resto del flusso di lavoro di approvazione.',
             },
         },
+        chooseWorkspace: "Scegli un'area di lavoro",
     },
     transactionMerge: {
         listPage: {
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 32e82e9d..852ec270 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -1042,12 +1042,12 @@ const translations = {
     receipt: {
         upload: '領収書をアップロード',
         uploadMultiple: '領収書をアップロード',
-        dragReceiptBeforeEmail: '領収書をこのページにドラッグするか、領収書を転送する',
-        dragReceiptsBeforeEmail: '領収書をこのページにドラッグするか、領収書を転送する',
-        dragReceiptAfterEmail: 'または、以下にアップロードするファイルを選択してください。',
+        dragReceiptBeforeEmail: 'このページにレシートをドラッグするか、レシートを転送する',
+        dragReceiptsBeforeEmail: 'このページに領収書をドラッグするか、領収書を転送する',
+        dragReceiptAfterEmail: 'または、以下のファイルを選択してアップロードしてください。',
         dragReceiptsAfterEmail: 'または、以下にアップロードするファイルを選択してください。',
         chooseReceipt: 'アップロードするレシートを選択するか、レシートを転送してください',
-        chooseReceipts: 'アップロードするレシートを選択するか、レシートを転送してください',
+        chooseReceipts: 'アップロードする領収書を選択するか、領収書を転送する',
         takePhoto: '写真を撮る',
         cameraAccess: '領収書の写真を撮るためにカメラへのアクセスが必要です。',
         deniedCameraAccess: 'カメラへのアクセスがまだ許可されていません。以下の手順に従ってください。',
@@ -1237,7 +1237,7 @@ const translations = {
         nextStep: '次のステップ',
         finished: '完了',
         sendInvoice: ({amount}: RequestAmountParams) => `${amount} 請求書を送信`,
-        submitAmount: ({amount}: RequestAmountParams) => `${amount}を提出`,
+        submitAmount: ({amount}: RequestAmountParams) => `${amount}を提出する`,
         expenseAmount: ({formattedAmount, comment}: RequestedAmountMessageParams) => `${formattedAmount}${comment ? `${comment} のために` : ''}`,
         submitted: ({memo}: SubmittedWithMemoParams) => `提出済み${memo ? `、次のように言って ${memo}` : ''}`,
         automaticallySubmitted: `<a href="${CONST.SELECT_WORKFLOWS_HELP_URL}">送信の遅延</a>を通じて送信されました`,
@@ -1460,6 +1460,7 @@ const translations = {
                 subtitle: '承認ワークフローの残りの部分を経由する前に、このレポートの追加の承認者を選択してください。',
             },
         },
+        chooseWorkspace: 'ワークスペースを選択',
     },
     transactionMerge: {
         listPage: {
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index e5496372..65bc9e59 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -1041,11 +1041,11 @@ const translations = {
         upload: 'Bonnetje uploaden',
         uploadMultiple: 'Bonnetjes uploaden',
         dragReceiptBeforeEmail: 'Sleep een bon naar deze pagina, stuur een bon door naar',
-        dragReceiptsBeforeEmail: 'Sleep bonnen naar deze pagina, stuur bonnen door naar',
-        dragReceiptAfterEmail: 'of kies hieronder een bestand om te uploaden.',
-        dragReceiptsAfterEmail: 'of kies hieronder bestanden om te uploaden.',
+        dragReceiptsBeforeEmail: 'Sleep bonnen naar deze pagina, stuur bonnen naar',
+        dragReceiptAfterEmail: 'of kies een bestand om hieronder te uploaden.',
+        dragReceiptsAfterEmail: 'of kies bestanden om hieronder te uploaden.',
         chooseReceipt: 'Kies een bon om te uploaden of stuur een bon door naar',
-        chooseReceipts: 'Kies bonnen om te uploaden of stuur bonnen door naar',
+        chooseReceipts: 'Kies bonnen om te uploaden of stuur bonnen naar',
         takePhoto: 'Maak een foto',
         cameraAccess: "Cameratoegang is vereist om foto's van bonnetjes te maken.",
         deniedCameraAccess: 'Camera-toegang is nog steeds niet verleend, volg alstublieft',
@@ -1235,7 +1235,7 @@ const translations = {
         nextStep: 'Volgende stappen',
         finished: 'Voltooid',
         sendInvoice: ({amount}: RequestAmountParams) => `Verstuur ${amount} factuur`,
-        submitAmount: ({amount}: RequestAmountParams) => `Verstuur ${amount}`,
+        submitAmount: ({amount}: RequestAmountParams) => `Verzend ${amount}`,
         expenseAmount: ({formattedAmount, comment}: RequestedAmountMessageParams) => `${formattedAmount}${comment ? `voor ${comment}` : ''}`,
         submitted: ({memo}: SubmittedWithMemoParams) => `ingediend${memo ? `, zegt ${memo}` : ''}`,
         automaticallySubmitted: `ingediend via <a href="${CONST.SELECT_WORKFLOWS_HELP_URL}">vertraging indieningen</a>`,
@@ -1460,6 +1460,7 @@ const translations = {
                 subtitle: 'Kies een extra goedkeurder voor dit rapport voordat we het via de rest van de goedkeuringsworkflow sturen.',
             },
         },
+        chooseWorkspace: 'Kies een werkruimte',
     },
     transactionMerge: {
         listPage: {
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index f776be16..965daa04 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -1040,7 +1040,7 @@ const translations = {
         upload: 'Prześlij paragon',
         uploadMultiple: 'Prześlij paragony',
         dragReceiptBeforeEmail: 'Przeciągnij paragon na tę stronę, prześlij paragon do',
-        dragReceiptsBeforeEmail: 'Przeciągnij paragony na tę stronę, prześlij paragony do',
+        dragReceiptsBeforeEmail: 'Przeciągnij paragony na tę stronę, prześlij paragony na',
         dragReceiptAfterEmail: 'lub wybierz plik do przesłania poniżej.',
         dragReceiptsAfterEmail: 'lub wybierz pliki do przesłania poniżej.',
         chooseReceipt: 'Wybierz paragon do przesłania lub prześlij paragon do',
@@ -1234,7 +1234,7 @@ const translations = {
         nextStep: 'Następne kroki',
         finished: 'Zakończono',
         sendInvoice: ({amount}: RequestAmountParams) => `Wyślij fakturę na kwotę ${amount}`,
-        submitAmount: ({amount}: RequestAmountParams) => `Zatwierdź ${amount}`,
+        submitAmount: ({amount}: RequestAmountParams) => `Prześlij ${amount}`,
         expenseAmount: ({formattedAmount, comment}: RequestedAmountMessageParams) => `${formattedAmount}${comment ? `dla ${comment}` : ''}`,
         submitted: ({memo}: SubmittedWithMemoParams) => `przesłano${memo ? `, mówiąc ${memo}` : ''}`,
         automaticallySubmitted: `przesłane za pomocą <a href="${CONST.SELECT_WORKFLOWS_HELP_URL}">opóźnij zgłoszenia</a>`,
@@ -1458,6 +1458,7 @@ const translations = {
                 subtitle: 'Wybierz dodatkowego zatwierdzającego dla tego raportu, zanim poprowadzimy go przez resztę przepływu pracy zatwierdzania.',
             },
         },
+        chooseWorkspace: 'Wybierz przestrzeń roboczą',
     },
     transactionMerge: {
         listPage: {
@@ -4804,7 +4805,7 @@ const translations = {
             textType: 'Tekst',
             dateType: 'Data',
             dropdownType: 'Lista',
-            formulaType: 'Formuła',
+            formulaType: 'Formula',
             textAlternateText: 'Dodaj pole do swobodnego wprowadzania tekstu.',
             dateAlternateText: 'Dodaj kalendarz do wyboru daty.',
             dropdownAlternateText: 'Dodaj listę opcji do wyboru.',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index aed4ddfc..bc405c94 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -660,7 +660,7 @@ const translations = {
         general: 'Geral',
         workspacesTabTitle: 'Workspaces',
         getTheApp: 'Obtenha o aplicativo',
-        scanReceiptsOnTheGo: 'Digitalize recibos com seu celular',
+        scanReceiptsOnTheGo: 'Digitalize recibos do seu celular',
         headsUp: 'Atenção!',
         submitTo: 'Enviar para',
         forwardTo: 'Encaminhar para',
@@ -1042,7 +1042,7 @@ const translations = {
         upload: 'Fazer upload de recibo',
         uploadMultiple: 'Fazer upload de recibos',
         dragReceiptBeforeEmail: 'Arraste um recibo para esta página, encaminhe um recibo para',
-        dragReceiptsBeforeEmail: 'Arraste recibos para esta página, encaminhe recibos para',
+        dragReceiptsBeforeEmail: 'Arraste os recibos para esta página, encaminhe os recibos para',
         dragReceiptAfterEmail: 'ou escolha um arquivo para enviar abaixo.',
         dragReceiptsAfterEmail: 'ou escolha arquivos para enviar abaixo.',
         chooseReceipt: 'Escolha um recibo para enviar ou encaminhe um recibo para',
@@ -1458,6 +1458,7 @@ const translations = {
                 subtitle: 'Escolha um aprovador adicional para este relatório antes de o encaminharmos através do restante do fluxo de trabalho de aprovação.',
             },
         },
+        chooseWorkspace: 'Escolha um espaço de trabalho',
     },
     transactionMerge: {
         listPage: {
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index a7a8b81f..ea47df00 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -659,7 +659,7 @@ const translations = {
         general: '常规',
         workspacesTabTitle: '工作区',
         getTheApp: '获取应用程序',
-        scanReceiptsOnTheGo: '用手机扫描收据',
+        scanReceiptsOnTheGo: '从手机扫描收据',
         headsUp: '注意!',
         submitTo: '提交到',
         forwardTo: '转发到',
@@ -1032,12 +1032,12 @@ const translations = {
     receipt: {
         upload: '上传收据',
         uploadMultiple: '上传收据',
-        dragReceiptBeforeEmail: '将收据拖到此页面上,转发收据到',
-        dragReceiptsBeforeEmail: '将收据拖到此页面上,转发收据到',
-        dragReceiptAfterEmail: '或选择下面的文件上传。',
+        dragReceiptBeforeEmail: '将收据拖到此页面上,或将收据转发至',
+        dragReceiptsBeforeEmail: '将收据拖到此页面上,转发收据至',
+        dragReceiptAfterEmail: '或选择一个文件上传。',
         dragReceiptsAfterEmail: '或选择下面的文件上传。',
-        chooseReceipt: '选择要上传的收据或转发收据到',
-        chooseReceipts: '选择要上传的收据或转发收据到',
+        chooseReceipt: '选择一个收据上传或转发收据到',
+        chooseReceipts: '选择收据进行上传或转发收据到',
         takePhoto: '拍照',
         cameraAccess: '需要相机权限来拍摄收据照片。',
         deniedCameraAccess: '相机访问权限仍未授予,请按照以下步骤操作',
@@ -1223,7 +1223,7 @@ const translations = {
         nextStep: '下一步',
         finished: '完成',
         sendInvoice: ({amount}: RequestAmountParams) => `发送 ${amount} 发票`,
-        submitAmount: ({amount}: RequestAmountParams) => `提交 ${amount}`,
+        submitAmount: ({amount}: RequestAmountParams) => `提交${amount}`,
         expenseAmount: ({formattedAmount, comment}: RequestedAmountMessageParams) => `${formattedAmount}${comment ? `对于${comment}` : ''}`,
         submitted: ({memo}: SubmittedWithMemoParams) => `已提交${memo ? `, 备注 ${memo}` : ''}`,
         automaticallySubmitted: `通过<a href="${CONST.SELECT_WORKFLOWS_HELP_URL}">延迟提交</a>提交`,
@@ -1442,6 +1442,7 @@ const translations = {
                 subtitle: '在我们将此报告路由到其余审批工作流之前,为此报告选择一个额外的审批人。',
             },
         },
+        chooseWorkspace: '选择一个工作区',
     },
     transactionMerge: {
         listPage: {
@@ -4716,7 +4717,7 @@ const translations = {
             textType: '文本',
             dateType: '日期',
             dropdownType: '列表',
-            formulaType: '公式',
+            formulaType: 'Formula',
             textAlternateText: '添加一个字段用于自由文本输入。',
             dateAlternateText: '添加日历以选择日期。',
             dropdownAlternateText: '添加一个选项列表供选择。',

Note

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

Copy link
Copy Markdown
Contributor

@grgia grgia left a comment

Choose a reason for hiding this comment

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

NAB, but why the translations change / this one as part of this PR?

@rushatgabhane
Copy link
Copy Markdown
Member

rushatgabhane commented Oct 14, 2025

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
    • MacOS: Desktop
  • 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 there are no new alerts related to the canBeMissing param for useOnyx
  • 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 image
Android: mWeb Chrome
iOS: HybridApp image
iOS: mWeb Safari image image
MacOS: Chrome / Safari
Screen.Recording.2025-10-14.at.04.58.51.mov
MacOS: Desktop

@melvin-bot melvin-bot bot requested a review from grgia October 14, 2025 03:00
@grgia grgia merged commit dfc733b into Expensify:main Oct 14, 2025
26 of 33 checks passed
@OSBotify
Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/grgia in version: 9.2.31-0 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@vincdargento
Copy link
Copy Markdown

@GCyganek The workspace list does not have a search bar at the top when there are more than 8 workspaces (this is how it currently works for manual expenses). Is this expected for the moment or should we create a new issue about this?

image

@mountiny
Copy link
Copy Markdown
Contributor

I dont think it is expected, every list should have the search bar over the limit of the items

@OSBotify
Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 9.2.31-2 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@GCyganek
Copy link
Copy Markdown
Contributor Author

@GCyganek The workspace list does not have a search bar at the top when there are more than 8 workspaces (this is how it currently works for manual expenses). Is this expected for the moment or should we create a new issue about this?

It looks like we haven't been showing the search bar even before the migration I did here, thanks for catching this

@grgia grgia mentioned this pull request Oct 20, 2025
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.

10 participants