Skip to content

Conversation

@JS00001
Copy link
Contributor

@JS00001 JS00001 commented Jan 27, 2026

Explanation of Change

Generate a system message for report actions when we have modified an expense via policy rules

Fixed Issues

$ #80522

Tests

N/A

  • Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

N/A

  • 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.
  • I verified that each 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

Screenshots/Videosundefined

@JS00001 JS00001 self-assigned this Jan 27, 2026
@JS00001 JS00001 requested review from a team as code owners January 27, 2026 00:37
@melvin-bot melvin-bot bot requested review from joekaufmanexpensify and sobitneupane and removed request for a team January 27, 2026 00:37
@melvin-bot
Copy link

melvin-bot bot commented Jan 27, 2026

@sobitneupane 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 January 27, 2026 00:37
@OSBotify

This comment has been minimized.

@JS00001 JS00001 requested review from cead22 and luacmartins January 27, 2026 00:40
@OSBotify

This comment has been minimized.

@JS00001 JS00001 changed the title [NO QA] Add an “applied a workspace rule” system message in expense details [HOLD Spanish[NO QA] Add an “applied a workspace rule” system message in expense details Jan 27, 2026
@JS00001 JS00001 changed the title [HOLD Spanish[NO QA] Add an “applied a workspace rule” system message in expense details [HOLD Spanish] [NO QA] Add an “applied a workspace rule” system message in expense details Jan 27, 2026
@JS00001 JS00001 changed the title [HOLD Spanish] [NO QA] Add an “applied a workspace rule” system message in expense details [NO QA] Add an “applied a workspace rule” system message in expense details Jan 27, 2026
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: 43c1701933

ℹ️ 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 on lines 205 to 206
const entries = Object.entries(policyRulesModifiedFields) as [keyof PolicyRulesModifiedFields, string | boolean][];

Choose a reason for hiding this comment

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

P2 Badge Handle policy tax values without stringifying objects

PolicyRulesModifiedFields includes tax?: Record<string, TaxRate> (see OriginalMessage.ts), but here the entries are cast to string | boolean and later passed to updatedFieldTo. When a workspace rule modifies taxes, the value is an object and will stringify to "[object Object]", producing a misleading system message. Consider explicitly formatting tax values or skipping object fields instead of assuming primitives.

Useful? React with 👍 / 👎.

@OSBotify

This comment has been minimized.

@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 210bdf56..bd617260 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -1497,23 +1497,23 @@ const translations: TranslationDeepObject<typeof en> = {
                     return value ? 'hat die Ausgabe als „erstattungsfähig“ markiert' : 'hat die Ausgabe als „nicht erstattungsfähig“ markiert';
                 }
                 if (key === 'billable') {
-                    return value ? 'hat die Ausgabe als „verrechenbar“ markiert' : 'hat die Ausgabe als „nicht abrechenbar“ markiert';
+                    return value ? 'hat die Ausgabe als „verrechenbar“ markiert' : 'hat die Ausgabe als „nicht verrechenbar“ markiert';
                 }
                 if (key === 'tax') {
                     const taxEntry = value as PolicyRulesModifiedFields['tax'];
                     const taxRateName = taxEntry?.field_id_TAX.name ?? '';
                     if (isFirst) {
-                        return `Steuersatz auf „${taxRateName}“ festlegen`;
+                        return `den Steuersatz auf „${taxRateName}“ festlegen`;
                     }
-                    return `Steuersatz zu „${taxRateName}“`;
+                    return `Steuersatz auf „${taxRateName}“`;
                 }
                 const updatedValue = value as string | boolean;
                 if (isFirst) {
-                    return `Setzen Sie ${translations.common[key].toLowerCase()} auf „${updatedValue}“`;
+                    return `setze ${translations.common[key].toLowerCase()} auf „${updatedValue}“`;
                 }
-                return `${translations.common[key].toLowerCase()} zu "${updatedValue}"`;
+                return `${translations.common[key].toLowerCase()} zu „${updatedValue}“`;
             });
-            return `${formatList(fragments)} über <a href="${policyRulesRoute}">Workspace-Regeln</a>`;
+            return `${formatList(fragments)} über <a href="${policyRulesRoute}">Arbeitsbereichsregeln</a>`;
         },
     },
     transactionMerge: {
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index ce2a0170..9b4cc909 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -1497,7 +1497,7 @@ const translations: TranslationDeepObject<typeof en> = {
             const fragments = entries.map(([key, value], i) => {
                 const isFirst = i === 0;
                 if (key === 'reimbursable') {
-                    return value ? 'a marqué la dépense comme « remboursable »' : 'a marqué la dépense comme « non remboursable »';
+                    return value ? 'a marqué la dépense comme « remboursable »' : 'a marqué la dépense comme « non remboursable »';
                 }
                 if (key === 'billable') {
                     return value ? 'a marqué la dépense comme « facturable »' : 'a marqué la dépense comme « non refacturable »';
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 2b128703..a2ba8068 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -1491,7 +1491,7 @@ const translations: TranslationDeepObject<typeof en> = {
             const fragments = entries.map(([key, value], i) => {
                 const isFirst = i === 0;
                 if (key === 'reimbursable') {
-                    return value ? 'ha contrassegnato la spesa come "rimborsabile"' : 'ha contrassegnato la spesa come "non rimborsabile"';
+                    return value ? 'ha contrassegnato la spesa come "rimborsabile"' : 'ha contrassegnato la spesa come “non rimborsabile”';
                 }
                 if (key === 'billable') {
                     return value ? 'ha contrassegnato la spesa come "fatturabile"' : 'ha contrassegnato la spesa come "non addebitabile"';
@@ -1502,7 +1502,7 @@ const translations: TranslationDeepObject<typeof en> = {
                     if (isFirst) {
                         return `imposta l'aliquota fiscale su "${taxRateName}"`;
                     }
-                    return `aliquota fiscale in "${taxRateName}"`;
+                    return `aliquota fiscale su "${taxRateName}"`;
                 }
                 const updatedValue = value as string | boolean;
                 if (isFirst) {
@@ -1510,7 +1510,7 @@ const translations: TranslationDeepObject<typeof en> = {
                 }
                 return `${translations.common[key].toLowerCase()} a "${updatedValue}"`;
             });
-            return `${formatList(fragments)} tramite <a href="${policyRulesRoute}">regole dello spazio di lavoro</a>`;
+            return `${formatList(fragments)} tramite <a href="${policyRulesRoute}">regole della workspace</a>`;
         },
     },
     transactionMerge: {
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index ce78c3ef..8d72afca 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -1489,10 +1489,10 @@ const translations: TranslationDeepObject<typeof en> = {
             const fragments = entries.map(([key, value], i) => {
                 const isFirst = i === 0;
                 if (key === 'reimbursable') {
-                    return value ? '経費を「立替精算対象」にマークしました' : '経費を「非精算」としてマークしました';
+                    return value ? '経費を「精算対象」としてマークしました' : 'この経費を「非精算」に設定しました';
                 }
                 if (key === 'billable') {
-                    return value ? '経費を「請求可能」とマークしました' : '経費を「請求対象外」としてマークしました';
+                    return value ? '経費を「請求可能」としてマークしました' : '経費を「請求対象外」にしました';
                 }
                 if (key === 'tax') {
                     const taxEntry = value as PolicyRulesModifiedFields['tax'];
@@ -1506,9 +1506,9 @@ const translations: TranslationDeepObject<typeof en> = {
                 if (isFirst) {
                     return `${translations.common[key].toLowerCase()} を「${updatedValue}」に設定`;
                 }
-                return `${translations.common[key].toLowerCase()} を「${updatedValue}」に`;
+                return `${translations.common[key].toLowerCase()} から「${updatedValue}」`;
             });
-            return `${formatList(fragments)}(<a href="${policyRulesRoute}">ワークスペースルール</a>経由)`;
+            return `${formatList(fragments)}(<a href="${policyRulesRoute}">ワークスペースルール</a> を介して)`;
         },
     },
     transactionMerge: {
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 3623ef42..c7159d60 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -1490,10 +1490,10 @@ const translations: TranslationDeepObject<typeof en> = {
             const fragments = entries.map(([key, value], i) => {
                 const isFirst = i === 0;
                 if (key === 'reimbursable') {
-                    return value ? 'heeft de uitgave als „vergoedbaar” gemarkeerd' : 'markeerde de uitgave als ‘niet-terugbetaalbaar’';
+                    return value ? 'heeft de uitgave gemarkeerd als “vergoedbaar”' : 'heeft de uitgave gemarkeerd als ‘niet-vergoedbaar’';
                 }
                 if (key === 'billable') {
-                    return value ? 'heeft de uitgave gemarkeerd als ‘factureerbaar’' : 'heeft de uitgave als ‘niet-declarabel’ gemarkeerd';
+                    return value ? 'heeft de uitgave als ‘factureerbaar’ gemarkeerd' : 'heeft de uitgave als ‘niet-factureerbaar’ gemarkeerd';
                 }
                 if (key === 'tax') {
                     const taxEntry = value as PolicyRulesModifiedFields['tax'];
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 2158f487..c5cb73e1 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -1489,10 +1489,10 @@ const translations: TranslationDeepObject<typeof en> = {
             const fragments = entries.map(([key, value], i) => {
                 const isFirst = i === 0;
                 if (key === 'reimbursable') {
-                    return value ? 'oznaczył wydatek jako „podlegający zwrotowi”' : 'oznaczył wydatek jako „niepodlegający zwrotowi”';
+                    return value ? 'oznaczył wydatek jako „podlegający zwrotowi”' : 'oznaczył(a) wydatek jako „niepodlegający zwrotowi”';
                 }
                 if (key === 'billable') {
-                    return value ? 'oznaczył wydatek jako „refakturowalny”' : 'oznaczył wydatek jako „niepodlegający refakturowaniu”';
+                    return value ? 'oznaczył wydatek jako „fakturowalny”' : 'oznaczył(-a) wydatek jako „niepodlegający refakturowaniu”';
                 }
                 if (key === 'tax') {
                     const taxEntry = value as PolicyRulesModifiedFields['tax'];
@@ -1500,15 +1500,15 @@ const translations: TranslationDeepObject<typeof en> = {
                     if (isFirst) {
                         return `ustaw stawkę podatku na „${taxRateName}”`;
                     }
-                    return `stawka podatku na „${taxRateName}”`;
+                    return `stawka podatkowa „${taxRateName}”`;
                 }
                 const updatedValue = value as string | boolean;
                 if (isFirst) {
                     return `ustaw ${translations.common[key].toLowerCase()} na „${updatedValue}”`;
                 }
-                return `${translations.common[key].toLowerCase()} na „${updatedValue}”`;
+                return `${translations.common[key].toLowerCase()} do „${updatedValue}”`;
             });
-            return `${formatList(fragments)} przez <a href="${policyRulesRoute}">zasady przestrzeni roboczej</a>`;
+            return `${formatList(fragments)} poprzez <a href="${policyRulesRoute}">zasady przestrzeni roboczej</a>`;
         },
     },
     transactionMerge: {
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 5097a2b6..b985d1a9 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -1487,18 +1487,18 @@ const translations: TranslationDeepObject<typeof en> = {
             const fragments = entries.map(([key, value], i) => {
                 const isFirst = i === 0;
                 if (key === 'reimbursable') {
-                    return value ? 'marcou a despesa como "reembolsável"' : 'marcou a despesa como “não reembolsável”';
+                    return value ? 'marcou a despesa como “reembolsável”' : 'marcou a despesa como "não reembolsável"';
                 }
                 if (key === 'billable') {
-                    return value ? 'marcou a despesa como “faturável”' : 'marcou a despesa como "não faturável"';
+                    return value ? 'marcou a despesa como “faturável”' : 'marcou a despesa como “não faturável”';
                 }
                 if (key === 'tax') {
                     const taxEntry = value as PolicyRulesModifiedFields['tax'];
                     const taxRateName = taxEntry?.field_id_TAX.name ?? '';
                     if (isFirst) {
-                        return `definir a taxa de imposto como "${taxRateName}"`;
+                        return `definir a taxa de imposto para "${taxRateName}"`;
                     }
-                    return `alíquota de imposto para "${taxRateName}"`;
+                    return `taxa de imposto para "${taxRateName}"`;
                 }
                 const updatedValue = value as string | boolean;
                 if (isFirst) {
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index d18cad80..374365d9 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -1466,10 +1466,10 @@ const translations: TranslationDeepObject<typeof en> = {
             const fragments = entries.map(([key, value], i) => {
                 const isFirst = i === 0;
                 if (key === 'reimbursable') {
-                    return value ? '将该报销单标记为“可报销”' : '将该报销单标记为“不可报销”';
+                    return value ? '将该报销单标记为“可报销”' : '已将该报销单标记为“不可报销”';
                 }
                 if (key === 'billable') {
-                    return value ? '将该报销标记为“可向客户收费”' : '已将该报销标记为“不可计费”';
+                    return value ? '将该报销标记为“可计费”' : '将该报销标记为“不可向客户计费”';
                 }
                 if (key === 'tax') {
                     const taxEntry = value as PolicyRulesModifiedFields['tax'];
@@ -1481,11 +1481,11 @@ const translations: TranslationDeepObject<typeof en> = {
                 }
                 const updatedValue = value as string | boolean;
                 if (isFirst) {
-                    return `将 ${translations.common[key].toLowerCase()} 设置为 “${updatedValue}”`;
+                    return `将 ${translations.common[key].toLowerCase()} 设置为“${updatedValue}”`;
                 }
                 return `${translations.common[key].toLowerCase()} 为 “${updatedValue}”`;
             });
-            return `${formatList(fragments)} 通过<a href="${policyRulesRoute}">工作区规则</a>`;
+            return `${formatList(fragments)},通过<a href="${policyRulesRoute}">工作区规则</a>`;
         },
     },
     transactionMerge: {

Note

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

@JS00001 JS00001 requested a review from situchan January 27, 2026 19:29
@situchan
Copy link
Contributor

situchan commented Jan 27, 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: mWeb Safari
MacOS: Chrome / Safari

cead22
cead22 previously requested changes Jan 27, 2026
Copy link
Contributor

@cead22 cead22 left a comment

Choose a reason for hiding this comment

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

Small change requested on the Spanish file

@situchan
Copy link
Contributor

Please merge main. Lint fixed in #80667

@chatgpt-codex-connector
Copy link

Codex Review: Didn't find any major issues. You're on a roll.

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

@situchan
Copy link
Contributor

There's no visual test on expense details as backend is not ready yet, right?

@JS00001
Copy link
Contributor Author

JS00001 commented Jan 27, 2026

@situchan no there are no visible tests yet

@situchan
Copy link
Contributor

@situchan no there are no visible tests yet

ok unit tests should cover this enough

@melvin-bot melvin-bot bot requested a review from carlosmiceli January 27, 2026 22:37
@melvin-bot
Copy link

melvin-bot bot commented Jan 27, 2026

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

@luacmartins luacmartins removed the request for review from carlosmiceli January 27, 2026 22:37
Copy link
Contributor

@luacmartins luacmartins left a comment

Choose a reason for hiding this comment

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

LGTM

@luacmartins luacmartins merged commit e80e190 into main Jan 27, 2026
36 checks passed
@luacmartins luacmartins deleted the jsenyitko-applied-workspace-rule branch January 27, 2026 22:42
@OSBotify
Copy link
Contributor

✋ 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/luacmartins in version: 9.3.11-0 🚀

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

None yet

Development

Successfully merging this pull request may close these issues.

6 participants