Skip to content

Conversation

@luacmartins
Copy link
Contributor

Explanation of Change

Adds a duplicate rule warning

Fixed Issues

$ #80526

Tests

Pre-condition: rules are enabled in the workspace

  1. Navigate to Workspace > Rules > Merchant
  2. Press Add merchant rule and create a new rule for merchant Expensify
  3. Press Add merchant rule and create a new rule for merchant Expensify again
  4. Verify that when you try to save, you see the modal below warning about a similar rule
  5. Verify that pressing Cancel dismisses the modal and takes you back to the rule editor
  6. Verify that pressing Save anyway saves the new rule
Screenshot 2026-01-28 at 8 16 51 PM
  • Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

Same as tests

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I 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

Screen.Recording.2026-01-28.at.8.23.48.PM.mov
Screenshot 2026-01-28 at 8 26 36 PM
Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

Add translations for the duplicate merchant rule warning modal in all
supported languages (en, es, de, fr, it, ja, nl, pl, pt-BR, zh-hans).
When saving a merchant rule, check if a rule with the same merchant name
and match type (contains/exact) already exists. If so, show a confirmation
modal asking the user if they want to save anyway.

- Add checkForDuplicateRule function to detect duplicates
- Show ConfirmModal with "Similar merchant rule already exists" title
- Allow user to proceed with "Save anyway" or cancel
- Exclude current rule when editing to avoid false positives
@luacmartins luacmartins self-assigned this Jan 29, 2026
@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 6ba4fc9f..d5b0f2f6 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -6410,7 +6410,7 @@ Fordere Spesendetails wie Belege und Beschreibungen an, lege Limits und Standard
                 matchTypeExact: 'Exakte Übereinstimmung',
                 expensesExactlyMatching: 'Für Ausgaben mit genau folgender Übereinstimmung:',
                 duplicateRuleTitle: 'Eine ähnliche Händlerregel existiert bereits',
-                duplicateRulePrompt: (merchantName: string) => `Möchten Sie eine neue Regel für „${merchantName}" speichern, obwohl Sie bereits eine bestehende haben?`,
+                duplicateRulePrompt: (merchantName: string) => `Möchten Sie eine neue Regel für „${merchantName}“ speichern, obwohl Sie bereits eine vorhandene haben?`,
                 saveAnyway: 'Trotzdem speichern',
             },
         },
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 899983a5..43c112a4 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -6420,8 +6420,8 @@ Exigez des informations de dépense comme les reçus et les descriptions, défin
                 matchTypeContains: 'Contient',
                 matchTypeExact: 'Correspond exactement',
                 expensesExactlyMatching: 'Pour les dépenses correspondant exactement :',
-                duplicateRuleTitle: 'Une règle commerçant similaire existe déjà',
-                duplicateRulePrompt: (merchantName: string) => `Voulez-vous enregistrer une nouvelle règle pour « ${merchantName} » même si vous en avez déjà une ?`,
+                duplicateRuleTitle: 'Une règle de commerçant similaire existe déjà',
+                duplicateRulePrompt: (merchantName: string) => `Voulez-vous enregistrer une nouvelle règle pour « ${merchantName} » même si vous en avez déjà une existante ?`,
                 saveAnyway: 'Enregistrer quand même',
             },
         },
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 9ca7c23d..6945dc44 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -6391,7 +6391,7 @@ Richiedi dettagli di spesa come ricevute e descrizioni, imposta limiti e valori
                 matchTypeContains: 'Contiene',
                 matchTypeExact: 'Corrisponde esattamente',
                 expensesExactlyMatching: 'Per le spese che corrispondono esattamente:',
-                duplicateRuleTitle: 'Esiste già una regola esercente simile',
+                duplicateRuleTitle: 'Esiste già una regola simile per questo commerciante',
                 duplicateRulePrompt: (merchantName: string) => `Vuoi salvare una nuova regola per "${merchantName}" anche se ne hai già una esistente?`,
                 saveAnyway: 'Salva comunque',
             },
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 32ac47e4..fc980246 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -6346,8 +6346,8 @@ ${reportName}
                 matchTypeContains: '含む',
                 matchTypeExact: '完全一致',
                 expensesExactlyMatching: '以下と完全一致する経費について:',
-                duplicateRuleTitle: '類似の取引先ルールが既に存在します',
-                duplicateRulePrompt: (merchantName: string) => `既存のルールがあるにもかかわらず、「${merchantName}」の新しいルールを保存しますか?`,
+                duplicateRuleTitle: '同じような支払先ルールがすでに存在します',
+                duplicateRulePrompt: (merchantName: string) => `既に既存のルールがありますが、「${merchantName}」用に新しいルールを保存しますか?`,
                 saveAnyway: 'それでも保存',
             },
         },
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index dffd4583..9d30706f 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -6379,8 +6379,8 @@ Vraag verplichte uitgavedetails zoals bonnetjes en beschrijvingen, stel limieten
                 matchTypeContains: 'Bevat',
                 matchTypeExact: 'Komt exact overeen',
                 expensesExactlyMatching: 'Voor uitgaven die exact overeenkomen met:',
-                duplicateRuleTitle: 'Er bestaat al een vergelijkbare handelaarsregel',
-                duplicateRulePrompt: (merchantName: string) => `Wilt u een nieuwe regel opslaan voor "${merchantName}" hoewel u al een bestaande heeft?`,
+                duplicateRuleTitle: 'Soortgelijke regel voor dezelfde handelaar bestaat al',
+                duplicateRulePrompt: (merchantName: string) => `Wilt je een nieuwe regel voor "${merchantName}" opslaan, ook al heb je al een bestaande?`,
                 saveAnyway: 'Toch opslaan',
             },
         },
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 378a93af..a3b0502f 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -6372,7 +6372,7 @@ Wymagaj szczegółów wydatków, takich jak paragony i opisy, ustawiaj limity i
                 matchTypeExact: 'Dokładne dopasowanie',
                 expensesExactlyMatching: 'Dla wydatków dokładnie pasujących:',
                 duplicateRuleTitle: 'Podobna reguła sprzedawcy już istnieje',
-                duplicateRulePrompt: (merchantName: string) => `Czy chcesz zapisać nową regułę dla „${merchantName}", mimo że masz już istniejącą?`,
+                duplicateRulePrompt: (merchantName: string) => `Czy chcesz zapisać nową regułę dla „${merchantName}”, mimo że masz już istniejącą?`,
                 saveAnyway: 'Zapisz mimo to',
             },
         },
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 76eea0c0..a52416a5 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -6371,8 +6371,8 @@ Exija detalhes de despesas como recibos e descrições, defina limites e padrõe
                 matchTypeContains: 'Contém',
                 matchTypeExact: 'Corresponde exatamente',
                 expensesExactlyMatching: 'Para despesas que correspondem exatamente:',
-                duplicateRuleTitle: 'Já existe uma regra de comerciante semelhante',
-                duplicateRulePrompt: (merchantName: string) => `Você deseja salvar uma nova regra para "${merchantName}" mesmo já tendo uma existente?`,
+                duplicateRuleTitle: 'Já existe uma regra semelhante para este comerciante',
+                duplicateRulePrompt: (merchantName: string) => `Você quer salvar uma nova regra para "${merchantName}", mesmo já tendo uma existente?`,
                 saveAnyway: 'Salvar mesmo assim',
             },
         },
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 04836288..256fd795 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -6236,9 +6236,9 @@ ${reportName}
                 matchTypeContains: '包含',
                 matchTypeExact: '完全匹配',
                 expensesExactlyMatching: '对于完全匹配以下条件的报销:',
-                duplicateRuleTitle: '已存在类似的商家规则',
-                duplicateRulePrompt: (merchantName: string) => `您想为「${merchantName}」保存一个新规则,即使您已有一个现有规则吗?`,
-                saveAnyway: '仍然保存',
+                duplicateRuleTitle: '类似的商家规则已存在',
+                duplicateRulePrompt: (merchantName: string) => `即使您已经有一个现有规则,是否仍要为“${merchantName}”保存新规则?`,
+                saveAnyway: '仍要保存',
             },
         },
         planTypePage: {

Note

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

@luacmartins luacmartins requested a review from situchan January 29, 2026 04:33
@luacmartins luacmartins marked this pull request as ready for review January 29, 2026 04:34
@luacmartins luacmartins requested review from a team as code owners January 29, 2026 04:34
@melvin-bot melvin-bot bot requested review from DylanDylann and JS00001 January 29, 2026 04:34
@luacmartins luacmartins requested review from cead22 and removed request for a team and DylanDylann January 29, 2026 04:34
@melvin-bot melvin-bot bot removed the request for review from a team January 29, 2026 04:34
@melvin-bot
Copy link

melvin-bot bot commented Jan 29, 2026

@DylanDylann @JS00001 One of you needs to 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 requested a review from heyjennahay January 29, 2026 04:34
@luacmartins
Copy link
Contributor Author

@codex review

@chatgpt-codex-connector
Copy link

Codex Review: Didn't find any major issues. What shall we delve into next?

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

@codecov
Copy link

codecov bot commented Jan 29, 2026

Codecov Report

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

Files with missing lines Coverage Δ
...space/rules/MerchantRules/MerchantRulePageBase.tsx 0.00% <0.00%> (ø)
... and 12 files with indirect coverage changes

Replace declarative ConfirmModal components with the useConfirmModal hook
for a cleaner imperative approach. This removes the need for modal visibility
state variables and simplifies the component.

Changes:
- Replace ConfirmModal imports with useConfirmModal hook
- Remove isDeleteModalVisible and isDuplicateWarningVisible state
- Use showConfirmModal() with promise chain for delete confirmation
- Use showConfirmModal() with promise chain for duplicate warning
- Remove ConfirmModal JSX from render
React Compiler automatically memoizes functions, making manual useCallback
wrappers unnecessary. Remove useCallback from checkForDuplicateRule and
saveRule functions.
@luacmartins luacmartins requested a review from situchan January 29, 2026 05:12
@luacmartins
Copy link
Contributor Author

Addressed comments

@situchan
Copy link
Contributor

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

@melvin-bot melvin-bot bot requested a review from rlinoz January 29, 2026 15:20
@melvin-bot
Copy link

melvin-bot bot commented Jan 29, 2026

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

@luacmartins luacmartins removed the request for review from rlinoz January 29, 2026 16:05
@luacmartins luacmartins merged commit fa3cd18 into main Jan 29, 2026
32 checks passed
@luacmartins luacmartins deleted the cmartins-dupeWarn branch January 29, 2026 17:40
@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-16 🚀

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.

5 participants