Skip to content

Stephanieelliott patch 18 1#73163

Merged
stephanieelliott merged 18 commits intostephanieelliott-patch-18from
stephanieelliott-patch-18-1
Oct 22, 2025
Merged

Stephanieelliott patch 18 1#73163
stephanieelliott merged 18 commits intostephanieelliott-patch-18from
stephanieelliott-patch-18-1

Conversation

@stephanieelliott
Copy link
Contributor

Explanation of Change

Fixed Issues

$
PROPOSAL:

Tests

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

  • 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
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop

@stephanieelliott stephanieelliott requested a review from a team as a code owner October 22, 2025 00:18
@stephanieelliott stephanieelliott merged commit 1e5b93b into stephanieelliott-patch-18 Oct 22, 2025
21 of 23 checks passed
@stephanieelliott stephanieelliott deleted the stephanieelliott-patch-18-1 branch October 22, 2025 00:18
@melvin-bot melvin-bot bot requested review from rlinoz and removed request for a team October 22, 2025 00:18
@melvin-bot
Copy link

melvin-bot bot commented Oct 22, 2025

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

NOTE: It looks like docs/redirects.csv was modified in this PR. Please see this SO for special instructions on how to review changes to that file.

@OSBotify
Copy link
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/fr.ts b/src/languages/fr.ts
index 1196fa98..854862f7 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -5394,7 +5394,6 @@ ${amount} pour ${merchant} - ${date}`,
                 `<muted-text-label>Pour activer la réconciliation continue, veuillez activer la <a href="${accountingAdvancedSettingsLink}">synchronisation automatique</a> pour ${connectionName}.</muted-text-label>`,
             chooseReconciliationAccount: {
                 chooseBankAccount: 'Choisissez le compte bancaire sur lequel les paiements de votre carte Expensify seront rapprochés.',
-
                 settlementAccountReconciliation: ({settlementAccountUrl, lastFourPAN}: SettlementAccountReconciliationParams) =>
                     `Assurez-vous que ce compte correspond à votre <a href="${settlementAccountUrl}">Compte de règlement de la carte Expensify</a> (terminant par ${lastFourPAN}) afin que la Réconciliation Continue fonctionne correctement.`,
             },
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 7eb2884e..4ba97d35 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -5396,7 +5396,6 @@ ${amount} per ${merchant} - ${date}`,
                 `<muted-text-label>Per abilitare la riconciliazione continua, abilita la <a href="${accountingAdvancedSettingsLink}">sincronizzazione automatica</a> per ${connectionName}.</muted-text-label>`,
             chooseReconciliationAccount: {
                 chooseBankAccount: 'Scegli il conto bancario su cui verranno riconciliati i pagamenti della tua carta Expensify.',
-
                 settlementAccountReconciliation: ({settlementAccountUrl, lastFourPAN}: SettlementAccountReconciliationParams) =>
                     `Assicurati che questo account corrisponda al tuo <a href="${settlementAccountUrl}">Conto di regolamento della carta Expensify</a> (terminante con ${lastFourPAN}) affinché la Riconciliazione Continua funzioni correttamente.`,
             },
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 6f21acbf..56b4ced3 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -5350,7 +5350,6 @@ ${date} - ${merchant}に${amount}`,
                 `<muted-text-label>継続的な照合を有効にするため、${connectionName}の<a href="${accountingAdvancedSettingsLink}">自動同期</a>を有効にしてください。</muted-text-label>`,
             chooseReconciliationAccount: {
                 chooseBankAccount: 'Expensifyカードの支払いを照合する銀行口座を選択してください。',
-
                 settlementAccountReconciliation: ({settlementAccountUrl, lastFourPAN}: SettlementAccountReconciliationParams) =>
                     `このアカウントがあなたの<a href="${settlementAccountUrl}">Expensifyカード決済口座</a>(${lastFourPAN}で終わる)と一致していることを確認してください。`,
             },
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 24b72e78..2419ffe4 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -5389,7 +5389,6 @@ ${amount} voor ${merchant} - ${date}`,
                 `<muted-text-label>Om continue afstemming mogelijk te maken, moet u <a href="${accountingAdvancedSettingsLink}">automatische synchronisatie</a> voor ${connectionName} inschakelen.</muted-text-label>`,
             chooseReconciliationAccount: {
                 chooseBankAccount: 'Kies de bankrekening waarmee uw Expensify Card-betalingen worden verrekend.',
-
                 settlementAccountReconciliation: ({settlementAccountUrl, lastFourPAN}: SettlementAccountReconciliationParams) =>
                     `Zorg ervoor dat dit account overeenkomt met uw <a href="${settlementAccountUrl}">Expensify Card afwikkelingsrekening</a> (eindigend op ${lastFourPAN}) zodat Continue Reconciliation goed werkt.`,
             },
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index b648dc70..5b670ae1 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -5378,7 +5378,6 @@ ${amount} dla ${merchant} - ${date}`,
                 `<muted-text-label>Aby włączyć funkcję ciągłego uzgadniania, włącz <a href="${accountingAdvancedSettingsLink}">automatyczną synchronizację</a> dla ${connectionName}.</muted-text-label>`,
             chooseReconciliationAccount: {
                 chooseBankAccount: 'Wybierz konto bankowe, z którym będą uzgadniane płatności kartą Expensify.',
-
                 settlementAccountReconciliation: ({settlementAccountUrl, lastFourPAN}: SettlementAccountReconciliationParams) =>
                     `Upewnij się, że to konto pasuje do Twojego <a href="${settlementAccountUrl}">Konto rozliczeniowe karty Expensify</a> (kończący się na ${lastFourPAN}), aby Ciągła Rekonsyliacja działała poprawnie.`,
             },
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 6e355462..c5d1abee 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -5380,7 +5380,6 @@ ${amount} para ${merchant} - ${date}`,
                 `<muted-text-label>Para ativar a reconciliação contínua, habilite a <a href="${accountingAdvancedSettingsLink}">sincronização automática</a> para o ${connectionName}.</muted-text-label>`,
             chooseReconciliationAccount: {
                 chooseBankAccount: 'Escolha a conta bancária na qual os pagamentos do seu Expensify Card serão reconciliados.',
-
                 settlementAccountReconciliation: ({settlementAccountUrl, lastFourPAN}: SettlementAccountReconciliationParams) =>
                     `Certifique-se de que esta conta corresponde à sua <a href="${settlementAccountUrl}">Conta de liquidação do Cartão Expensify</a> (terminando em ${lastFourPAN}) para que a Reconciliação Contínua funcione corretamente.`,
             },
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 5374e622..0dc051ed 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -5289,7 +5289,6 @@ ${merchant}的${amount} - ${date}`,
                 `<muted-text-label>要启用持续对账,请启用 ${connectionName} 的<a href="${accountingAdvancedSettingsLink}">自动同步</a>功能。</muted-text-label>`,
             chooseReconciliationAccount: {
                 chooseBankAccount: '选择用于对账您的 Expensify Card 支付的银行账户。',
-
                 settlementAccountReconciliation: ({settlementAccountUrl, lastFourPAN}: SettlementAccountReconciliationParams) =>
                     `确保此账户与您的<a href="${settlementAccountUrl}">Expensify Card 结算账户</a>(以 ${lastFourPAN} 结尾)匹配,以便持续对账正常工作。`,
             },

Note

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

@github-actions
Copy link
Contributor

LGTM :feelsgood:. Thank you for your hard work!

@github-actions
Copy link
Contributor

HelpDot Documentation Review

Assessment Summary

After thorough analysis of PR #73163, this pull request does not contain HelpDot documentation changes that require a HelpDot documentation quality review.

PR Content Analysis

This PR is a technical implementation focused on:

  1. react-native-web Library Update: Upgrading from v0.20.0 to v0.21.2
  2. Patch File Management: Updating and renaming patch files to match the new library version
  3. UI Component Refactoring: Improving the focus mode notification component with better HTML rendering
  4. URL Redirect Configuration: Minor updates to docs/redirects.csv (infrastructure, not user documentation)

Files Reviewed

  • 29 files changed (71 additions, 74 deletions)
  • No HelpDot documentation files (.md files in docs/articles/) were modified
  • Changes are primarily in: patches/, src/components/, src/languages/, package files

Recommendation

This PR should be reviewed by:

  • Technical reviewers for the react-native-web upgrade and component changes
  • QA team for testing the focus mode notification functionality across platforms

No HelpDot documentation review is needed as this PR does not modify user-facing help documentation.


This assessment was generated by the HelpDot Documentation Review Bot. For questions about HelpDot documentation reviews, please refer to the documentation review guidelines.

@codecov
Copy link

codecov bot commented Oct 22, 2025

Codecov Report

❌ Patch coverage is 46.26374% with 489 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
...eceiptPartners/ChangeReceiptBillingAccountPage.tsx 0.00% 54 Missing ⚠️
src/libs/SearchParser/autocompleteParser.js 71.60% 46 Missing ⚠️
src/pages/Travel/TravelTerms.tsx 0.00% 30 Missing ⚠️
...rovals/WorkspaceWorkflowsApprovalsApproverPage.tsx 0.00% 30 Missing ⚠️
src/components/ApproverSelectionList.tsx 0.00% 29 Missing ⚠️
src/pages/ReportAddApproverPage.tsx 0.00% 26 Missing ⚠️
src/pages/settings/Profile/Avatar/AvatarPage.tsx 0.00% 26 Missing ⚠️
...ls/WorkspaceWorkflowsApprovalsExpensesFromPage.tsx 0.00% 20 Missing ⚠️
src/libs/SearchParser/searchParser.js 88.88% 18 Missing ⚠️
src/components/Search/index.tsx 0.00% 14 Missing ⚠️
... and 69 more
Files with missing lines Coverage Δ
src/CONST/index.ts 85.84% <ø> (ø)
src/SCREENS.ts 100.00% <ø> (ø)
src/components/AttachmentModal.tsx 0.53% <ø> (ø)
src/components/AttachmentPicker/index.native.tsx 20.30% <ø> (ø)
src/components/AttachmentPicker/index.tsx 0.00% <ø> (ø)
src/components/AvatarWithImagePicker.tsx 24.13% <ø> (+20.13%) ⬆️
...omponents/Composer/implementation/index.native.tsx 58.33% <ø> (ø)
src/components/FilePicker/index.native.tsx 0.00% <ø> (ø)
...components/ImportOnyxState/BaseImportOnyxState.tsx 0.00% <ø> (ø)
src/components/ImportOnyxState/index.native.tsx 0.00% <ø> (ø)
... and 176 more

... and 1246 files with indirect coverage changes

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

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.2.37-1 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/blimpich in version: 9.2.37-8 🚀

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

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.

6 participants