Skip to content

[Domain control] [Release 2] Remove Members "beta" - add Domain members button#80090

Merged
mountiny merged 8 commits intoExpensify:mainfrom
software-mansion-labs:war-in/add-members-button
Feb 5, 2026
Merged

[Domain control] [Release 2] Remove Members "beta" - add Domain members button#80090
mountiny merged 8 commits intoExpensify:mainfrom
software-mansion-labs:war-in/add-members-button

Conversation

@war-in
Copy link
Contributor

@war-in war-in commented Jan 21, 2026

Explanation of Change

Fixed Issues

$ #79901
PROPOSAL:

Tests

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

  • 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 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 image

@melvin-bot
Copy link

melvin-bot bot commented Jan 21, 2026

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

@codecov
Copy link

codecov bot commented Jan 21, 2026

Codecov Report

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

Files with missing lines Coverage Δ
...n/AppNavigator/Navigators/DomainSplitNavigator.tsx 0.00% <ø> (ø)
src/pages/domain/DomainInitialPage.tsx 0.00% <0.00%> (ø)
src/pages/domain/Members/DomainAddMemberPage.tsx 0.00% <0.00%> (ø)
... and 93 files with indirect coverage changes

# Conflicts:
#	src/libs/Navigation/AppNavigator/Navigators/DomainSplitNavigator.tsx
#	src/pages/domain/DomainInitialPage.tsx
@war-in war-in moved this from In Progress to Ready for Review in Bring Domain Control to NewDot Jan 28, 2026
@war-in war-in marked this pull request as ready for review January 28, 2026 09:35
@war-in war-in requested review from a team as code owners January 28, 2026 09:35
@melvin-bot
Copy link

melvin-bot bot commented Jan 28, 2026

@situchan 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 request for a team January 28, 2026 09:35
Copy link

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

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: 623f996aea

ℹ️ 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".

@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/de.ts b/src/languages/de.ts
index 4348d6af..1bd54b3e 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -6995,7 +6995,7 @@ Fordere Spesendetails wie Belege und Beschreibungen an, lege Limits und Standard
                 [CONST.SEARCH.GROUP_BY.CARD]: 'Karte',
                 [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'Auszahlungs-ID',
                 [CONST.SEARCH.GROUP_BY.CATEGORY]: 'Kategorie',
-                [CONST.SEARCH.GROUP_BY.TAG]: 'Stichwort',
+                [CONST.SEARCH.GROUP_BY.TAG]: 'Tag',
                 [CONST.SEARCH.GROUP_BY.MONTH]: 'Monat',
             },
             feed: 'Feed',
@@ -8152,6 +8152,7 @@ Hier ist ein *Testbeleg*, um dir zu zeigen, wie es funktioniert:`,
             errors: {addMember: 'Dieses Mitglied kann nicht hinzugefügt werden. Bitte versuche es erneut.'},
         },
         domainAdmins: 'Domain-Admins',
+        domainMembers: 'Domänenmitglieder',
     },
     gps: {
         disclaimer: 'Benutze GPS, um eine Ausgabe von deiner Reise zu erstellen. Tippe unten auf „Start“, um mit der Aufzeichnung zu beginnen.',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 4b1b8264..9808d3c7 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -8158,6 +8158,7 @@ Voici un *reçu test* pour vous montrer comment cela fonctionne :`,
             errors: {addMember: 'Impossible d’ajouter ce membre. Veuillez réessayer.'},
         },
         domainAdmins: 'Administrateurs de domaine',
+        domainMembers: 'Membres du domaine',
     },
     gps: {
         disclaimer: 'Utilisez le GPS pour créer une dépense à partir de votre trajet. Touchez Démarrer ci-dessous pour commencer le suivi.',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 8ef5103b..a5b2228b 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -8139,6 +8139,7 @@ Ecco una *ricevuta di prova* per mostrarti come funziona:`,
             errors: {addMember: 'Impossibile aggiungere questo membro. Riprova.'},
         },
         domainAdmins: 'Amministratori di dominio',
+        domainMembers: 'Membri del dominio',
     },
     gps: {
         disclaimer: 'Usa il GPS per creare una spesa dal tuo viaggio. Tocca Avvia qui sotto per iniziare il tracciamento.',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 29398886..bb3faf4e 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -6921,7 +6921,7 @@ ${reportName}
             reimbursable: '精算対象',
             purchaseCurrency: '購入通貨',
             groupBy: {
-                [CONST.SEARCH.GROUP_BY.FROM]: '送信者',
+                [CONST.SEARCH.GROUP_BY.FROM]: '差出人',
                 [CONST.SEARCH.GROUP_BY.CARD]: 'カード',
                 [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: '出金ID',
                 [CONST.SEARCH.GROUP_BY.CATEGORY]: 'カテゴリ',
@@ -8072,6 +8072,7 @@ Expensify の使い方をお見せするための*テストレシート*がこ
             errors: {addMember: 'このメンバーを追加できませんでした。もう一度お試しください。'},
         },
         domainAdmins: 'ドメイン管理者',
+        domainMembers: 'ドメインメンバー',
     },
     gps: {
         disclaimer: '移動中の経路から、GPS を使って経費を作成しましょう。下の「開始」をタップして追跡を始めてください。',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index a29f8bac..171ae2c2 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -8121,6 +8121,7 @@ Hier is een *testbon* om je te laten zien hoe het werkt:`,
             errors: {addMember: 'Kan dit lid niet toevoegen. Probeer het opnieuw.'},
         },
         domainAdmins: 'Domeinbeheerders',
+        domainMembers: 'Domeinleden',
     },
     gps: {
         disclaimer: 'Gebruik GPS om een uitgave van je reis te maken. Tik hieronder op Start om het volgen te beginnen.',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 67b0050f..c7b78213 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -6957,7 +6957,7 @@ Wymagaj szczegółów wydatków, takich jak paragony i opisy, ustawiaj limity i
                 [CONST.SEARCH.GROUP_BY.CARD]: 'Karta',
                 [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'ID wypłaty',
                 [CONST.SEARCH.GROUP_BY.CATEGORY]: 'Kategoria',
-                [CONST.SEARCH.GROUP_BY.TAG]: 'Etykieta',
+                [CONST.SEARCH.GROUP_BY.TAG]: 'Tag',
                 [CONST.SEARCH.GROUP_BY.MONTH]: 'Miesiąc',
             },
             feed: 'Kanał',
@@ -8106,6 +8106,7 @@ Oto *paragon testowy*, który pokazuje, jak to działa:`,
             errors: {addMember: 'Nie można dodać tego członka. Spróbuj ponownie.'},
         },
         domainAdmins: 'Administratorzy domeny',
+        domainMembers: 'Członkowie domeny',
     },
     gps: {
         disclaimer: 'Użyj GPS, aby utworzyć wydatek z Twojej podróży. Stuknij „Start” poniżej, aby rozpocząć śledzenie.',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 6251c0b9..21a623f4 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -6956,7 +6956,7 @@ Exija detalhes de despesas como recibos e descrições, defina limites e padrõe
             groupBy: {
                 [CONST.SEARCH.GROUP_BY.FROM]: 'De',
                 [CONST.SEARCH.GROUP_BY.CARD]: 'Cartão',
-                [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'ID da retirada',
+                [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'ID de saque',
                 [CONST.SEARCH.GROUP_BY.CATEGORY]: 'Categoria',
                 [CONST.SEARCH.GROUP_BY.TAG]: 'Etiqueta',
                 [CONST.SEARCH.GROUP_BY.MONTH]: 'Mês',
@@ -8110,6 +8110,7 @@ Aqui está um *recibo de teste* para mostrar como funciona:`,
             errors: {addMember: 'Não foi possível adicionar este membro. Tente novamente.'},
         },
         domainAdmins: 'Administradores de domínio',
+        domainMembers: 'Membros do domínio',
     },
     gps: {
         disclaimer: 'Use o GPS para criar uma despesa a partir da sua viagem. Toque em Iniciar abaixo para começar o rastreamento.',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 4bfcf7b5..54c6c3ed 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -6802,7 +6802,7 @@ ${reportName}
             purchaseCurrency: '购买货币',
             groupBy: {
                 [CONST.SEARCH.GROUP_BY.FROM]: '来自',
-                [CONST.SEARCH.GROUP_BY.CARD]: '卡片',
+                [CONST.SEARCH.GROUP_BY.CARD]: '卡',
                 [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: '提现 ID',
                 [CONST.SEARCH.GROUP_BY.CATEGORY]: '类别',
                 [CONST.SEARCH.GROUP_BY.TAG]: '标签',
@@ -7907,6 +7907,7 @@ ${reportName}
         },
         members: {title: '成员', findMember: '查找成员', addMember: '添加成员', email: '电子邮箱地址', errors: {addMember: '无法添加此成员。请重试。'}},
         domainAdmins: '域管理员',
+        domainMembers: '域成员',
     },
     gps: {
         disclaimer: '使用 GPS 根据您的行程创建报销。点击下方的“开始”以开始跟踪。',

Note

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

@mountiny
Copy link
Contributor

@dubielzyk-expensify we are still waiting for the close account and add member flow to be added but this will be the Release 2 PR that enables it for the users so the one for you to help review 🙌

Copy link
Contributor

@joekaufmanexpensify joekaufmanexpensify left a comment

Choose a reason for hiding this comment

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

Wn project

@github-actions
Copy link
Contributor

🚧 @mountiny has triggered a test Expensify/App build. You can view the workflow run here.

@github-actions

This comment has been minimized.

@dubielzyk-expensify
Copy link
Contributor

dubielzyk-expensify commented Jan 29, 2026

Given the position of the domain I wonder if we should add the ability that doesn't allow adding @ symbol cause you can end up in this position that feels weird. I assume people will grok it after some time, but by not allowing the @ I feel they'll realise quicker. Thoughts @Expensify/design

CleanShot 2026-01-29 at 10 24 41@2x

@dannymcclain
Copy link
Contributor

No strong feelings from me. Definitely not against it, but also don't feel like it's super critical. If you think it would save people some time/confusion/headache though, I'm down.

@shawnborton
Copy link
Contributor

Neat idea for sure, I also don't feel too strongly though. If it's easy to implement, seems like it would be a nice UX improvement.

@dubielzyk-expensify
Copy link
Contributor

Cool. Let's hear from @war-in and if not, the we'll leave it as is 👍

@war-in
Copy link
Contributor Author

war-in commented Jan 30, 2026

It can be fairly easily implemented - done in the latest commit

Screen.Recording.2026-01-30.at.10.29.52.mov

<TextInput
ref={ref}
onChangeText={(value: string) => {
onInputChange?.(value.replaceAll('@', ''));
Copy link
Contributor

@ZhenjaHorbach ZhenjaHorbach Jan 30, 2026

Choose a reason for hiding this comment

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

I think we can add an explanation of why we replace @

Copy link
Contributor

@ZhenjaHorbach ZhenjaHorbach Jan 30, 2026

Choose a reason for hiding this comment

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

And do we really need a separate Input component?
I suppose we can use onInputChange param with this logic for InputWrapper with InputComponent={TextInput}

Copy link
Contributor Author

Choose a reason for hiding this comment

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

we could do that but we would have to keep the email state in DomainAddMemberPage which we don't do currently

// Inside DomainAddMemberPage
const [email, setEmail] = useState('');
 
const handleEmailChange = (value: string) => {
    setEmail(value.replaceAll('@', ''));
};

// ...

<InputWrapper
    InputComponent={TextInput}
    inputID={INPUT_IDS.EMAIL}
    value={email}
    onChangeText={handleEmailChange}
    // ... rest of props
/>

I think the separate input component fits well but let's ask @situchan for thoughts?

Copy link
Contributor

@ZhenjaHorbach ZhenjaHorbach Feb 5, 2026

Choose a reason for hiding this comment

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

Actually, do we need to use the same logic on DomainAddAdminPage screen?
If yes, then separate TextInput looks good!

Copy link
Contributor

Choose a reason for hiding this comment

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

I am fine with current change

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Actually, do we need to use the same logic on DomainAddAdminPage screen?

Unfortunately, no :/
This screen has only one text input and doesn't use selection list like the add admin page does

Copy link
Contributor

Choose a reason for hiding this comment

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

Okay then
let's leave it as is!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

after this message I started experimenting with masked input but I think this might be an overkill for our usecase

@mountiny mountiny changed the title [Domain control] [Release 2] Remove Members "beta" - add Domain members button [HOL] [Domain control] [Release 2] Remove Members "beta" - add Domain members button Feb 2, 2026
@mountiny mountiny changed the title [HOL] [Domain control] [Release 2] Remove Members "beta" - add Domain members button [HOLD https://github.com/Expensify/App/pull/78002] [Domain control] [Release 2] Remove Members "beta" - add Domain members button Feb 2, 2026
# Conflicts:
#	src/languages/de.ts
#	src/languages/fr.ts
#	src/languages/it.ts
#	src/languages/ja.ts
#	src/languages/nl.ts
#	src/languages/pl.ts
#	src/languages/pt-BR.ts
#	src/languages/zh-hans.ts
@war-in war-in changed the title [HOLD https://github.com/Expensify/App/pull/78002] [Domain control] [Release 2] Remove Members "beta" - add Domain members button [Domain control] [Release 2] Remove Members "beta" - add Domain members button Feb 5, 2026
@situchan
Copy link
Contributor

situchan commented Feb 5, 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
    • 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
Android: mWeb Chrome
iOS: HybridApp
ios.mov
iOS: mWeb Safari
msafari.mov
MacOS: Chrome / Safari
web.mov

@situchan
Copy link
Contributor

situchan commented Feb 5, 2026

This is limitation in RN so not blocker

native.mov

Copy link
Contributor

@mountiny mountiny left a comment

Choose a reason for hiding this comment

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

Lets get this one out!

@mountiny mountiny merged commit bd36b36 into Expensify:main Feb 5, 2026
36 of 38 checks passed
@github-project-automation github-project-automation bot moved this from Ready for Review to Done in Bring Domain Control to NewDot Feb 5, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Feb 5, 2026

🚧 @mountiny has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify
Copy link
Contributor

OSBotify commented Feb 5, 2026

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/mountiny in version: 9.3.16-0 🚀

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

@izarutskaya
Copy link

Hi @war-in Do we need QA for this? Thanks

@war-in
Copy link
Contributor Author

war-in commented Feb 10, 2026

@mountiny do you have tests for Release 2? I think you added them last time (release 1). Thank you!

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/lakchote in version: 9.3.16-9 🚀

platform result
🕸 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

Development

Successfully merging this pull request may close these issues.

10 participants

Comments