Skip to content

Vendor matching CC - R1: App Phase 3 (expense flow UI)#91886

Draft
Beamanator wants to merge 4 commits into
mainfrom
beaman-vendor-matching-r1-app-phase-3
Draft

Vendor matching CC - R1: App Phase 3 (expense flow UI)#91886
Beamanator wants to merge 4 commits into
mainfrom
beaman-vendor-matching-r1-app-phase-3

Conversation

@Beamanator
Copy link
Copy Markdown
Contributor

@Beamanator Beamanator commented May 27, 2026

Explanation of Change

Phase 3 of Vendor matching CC - R1: App — the user-facing expense-flow UI. With this PR the end-to-end R1 flow is in place: an admin enables the vendorMatching beta on a QBO + Credit/Debit-card workspace, the PHP fuzzy matcher (already on staging via the Web-Expensify commands and event hooks PR) writes comment.vendor on incoming non-reimbursable expenses, and submitters/approvers can see + manually override the matched vendor on every expense.

Four chunks, four commits:

  1. IOURequestStepVendor RHP + nav wiring — new searchable vendor selector. Builds the list from getQBOVendors(policy) (Phase 1 helper), filters by name, and on selection calls updateMoneyRequestVendor(transactionID, vendorID, transaction) — the Phase 1 action that handles the optimistic comment.vendor write + the optimistic inactiveVendor violation clear. Adds the standard nav surface: SCREENS.MONEY_REQUEST.STEP_VENDOR, ROUTES.MONEY_REQUEST_STEP_VENDOR, the param type, linking config, modal-stack entry, and the screen-name union in both withWritableReportOrNotFound and withFullTransactionOrNotFound. New common.vendor translation in all 10 supported locales.

  2. Vendor row on MoneyRequestView — surfaces the current vendor below the Category row. shouldShowVendor = hasVendorFeature(policy, isBetaEnabled(BETAS.VENDOR_MATCHING)) && !isCurrentTransactionReimbursable, so the row only appears on non-reimbursable expenses for workspaces with the beta + QBO Credit/Debit-card config. Title resolves via getQBOVendorByID(policy, transaction?.comment?.vendor?.externalID)?.name — empty when the matched vendor has since been removed from QBO. Tapping the row opens the new RHP. The inactiveVendor violation auto-surfaces via getErrorForField('vendor') because Phase 1 already mapped inactiveVendor → 'vendor' in useViolations.ts.

  3. CONCIERGEAUTOMATCHVENDOR action rendering — new App-side surface for the Concierge system message that Phase 1 Auth emits when the PHP matcher writes an auto-match. Adds CONST.REPORT.ACTIONS.TYPE.CONCIERGE_AUTO_MATCH_VENDOR, the OriginalMessageConciergeAutoMatchVendor type (vendorName for display + reasoning for the LLM-consumable explanation), a new ConciergeAutoMatchVendorContent renderer, and the route entry in ActionContentRouter. Reuses ReportActionItemMessageWithExplain, which automatically appends the "Explain" link whenever the action's originalMessage has a reasoning field — clicking opens a Concierge thread that explains the match. New iou.conciergeAutoMatchedVendor translation in all 10 locales.

  4. Cleanup — drops the deprecated getUrlWithBackToParam from the new route per contributingGuides/NAVIGATION.md (would have tripped the eslint-seatbelt baseline by 1); removes an unused CONST import.

Phase 1 / Phase 2 dependencies that are already merged

  • App Phase 1 PR — types, constants, updateMoneyRequestVendor action, BETAS.VENDOR_MATCHING gate, inactiveVendor violation client-compute. Phase 3 is a thin layer over the Phase 1 surface.
  • App Phase 2 PR — Default vendor row in QBO CC export settings. Independent of Phase 3; either can ship first.
  • Auth foundation PR (merged + deployed) — the vendor NVP + UpdateMoneyRequestVendor Auth command + ACTION_CONCIERGE_AUTO_MATCH_VENDOR constant.
  • Web-Expensify commands and event hooks PR (merged, awaiting deploy) — the PHP fuzzy matcher + Concierge auto-match action emission.

What's NOT in this PR (intentional Phase 4 / R2 work)

  • Java QBO exporter read of comment.vendor.externalID instead of merchant-string matching — Integration-Server has a BetaManager but it gates on hardcoded policy IDs, not workspace betas[]. We're shipping Java as a clean unconditional cutover at R1 GA rather than introducing a parallel hardcoded-IDs path.
  • pushTransactionViolationsOnyxData callers on QBO export-type change + vendor-list sync (deferred from Phase 2) — still requires either refactoring out of updateManyPolicyConnectionConfigs or a new Onyx subscriber pattern. Zero workspaces on the beta today; violations recompute lazily on next transaction edit.
  • Workspace Vendors tab (deferred from Phase 2) — read-only display of the imported QBO vendor list. The Phase 3 vendor selector RHP already exposes the same data to expense submitters/approvers, so the workspace tab is a "settings preview" rather than load-bearing for R1.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/638653

PROPOSAL: N/A (internal feature, no external proposal)

Tests

Prerequisite: a workspace with the vendorMatching beta enabled, QBO connected, and non-reimbursable export destination set to Credit Card or Debit Card. The PHP fuzzy matcher needs to be on the environment for the auto-match path; the manual-pick path works regardless.

Manual vendor pick path:

  1. Create a non-reimbursable expense on a QBO + CC/DC workspace and open it.
  2. Verify the new Vendor row appears on the expense detail view below Category and is editable (right caret showing).
  3. Tap the Vendor row. Verify a searchable list of vendors opens.
  4. Type a partial vendor name. Verify the list filters by name.
  5. Select a vendor. Verify the RHP closes and the Vendor row title updates to the picked name.
  6. Reopen the Vendor row. Verify the previously-selected vendor is initially focused.
  7. With the vendorMatching beta disabled on the workspace, verify the Vendor row is hidden.
  8. With the workspace QBO export destination flipped to Vendor Bill, verify the Vendor row is hidden.
  9. With the expense flipped to reimbursable, verify the Vendor row is hidden.

Auto-match path (requires the Web-Expensify PHP fuzzy matcher PR on the environment + vendorMatching beta opted in):

  1. Import a non-reimbursable card transaction whose merchant name fuzzy-matches a QBO vendor (e.g. ACME*1234 against Acme Corp).
  2. Open the resulting transaction thread.
  3. Verify a Concierge system message reading "Concierge matched this expense to Acme Corp" appears, with an Explain link.
  4. Tap Explain. Verify Concierge opens a thread that reveals the match reasoning (the reasoning field on the action's originalMessage).
  5. Open the expense detail. Verify the Vendor row now shows Acme Corp.

Inactive vendor violation path:

  1. With an expense that has a vendor set, delete that vendor in QBO and re-sync the connection.
  2. Reopen the expense. Verify the Vendor row shows a brick-road indicator and the violation message ("[vendor] no longer valid").
  3. Tap the Vendor row and pick any active vendor. Verify the violation clears.
  • Verify that no errors appear in the JS console

Offline tests

Same as Tests, executed with the network disabled after step 1. Verify the manual-pick flow surfaces the standard OfflineWithFeedback pending-action indicator on the Vendor row, and that the optimistic vendor update (and optimistic inactiveVendor violation clear) from Phase 1's action persist correctly when the connection returns.

QA Steps

Same as Tests, but on staging with the vendorMatching beta enabled. Internal QA only — feature is gated by beta opt-in and only meaningful on workspaces with QBO + CC/DC export.

  • 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 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 similar component doesn't exist in the codebase
  • I verified that all props are defined accurately and each prop has a /** comment above it */
  • I verified that each file is named correctly
  • I verified that each component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • I verified that the only data being stored in component state is data necessary for rendering and nothing else
  • In component if we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
  • 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)
  • I verified that component 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)
  • I verified that all JSX used for rendering exists in the render method
  • 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/Videos

To be added once a local build is up. The new UI surfaces are: the Vendor row on MoneyRequestView, the IOURequestStepVendor RHP, and the ConciergeAutoMatchVendor system message in the transaction thread.

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

New vendor selector RHP that lists QBO vendors with name search and writes
the user pick via the Phase 1 updateMoneyRequestVendor action (isManuallySet
hardcoded true). Wires the screen, route, navigation type, linking config,
modal-stack registration, withWritableReportOrNotFound + withFullTransactionOrNotFound
union members, and adds the common.vendor translation in all 10 supported
locales.
Surfaces the current expense vendor below the Category row when the
workspace has the vendorMatching beta + QBO Credit/Debit-card export
config AND the expense is non-reimbursable. Tapping opens the new
MONEY_REQUEST_STEP_VENDOR RHP. The inactiveVendor violation is surfaced
via getErrorForField('vendor') using the Phase 1 useViolations mapping
(inactiveVendor → 'vendor' field).
Wires the App side of the Phase 1 Auth-emitted CONCIERGEAUTOMATCHVENDOR
report action: new CONST entry, OriginalMessage type (vendorName +
reasoning), renderer using ReportActionItemMessageWithExplain (Explain
link surfaces automatically via hasReasoning check), and translations
across all 10 supported locales.
Removes getUrlWithBackToParam usage from the new route (the deprecated
backTo pattern, per contributingGuides/NAVIGATION.md) and removes the
unused CONST import in ConciergeAutoMatchVendorContent. Navigation back
from the RHP just closes the modal, returning to the previous view.
@OSBotify
Copy link
Copy Markdown
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 e9dbd702836..3dfceb92d8b 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -314,7 +314,7 @@ const translations: TranslationDeepObject<typeof en> = {
         merchant: 'Händler',
         change: 'Ändern',
         category: 'Kategorie',
-        vendor: 'Anbieter',
+        vendor: 'Lieferant',
         report: 'Bericht',
         billable: 'Abrechenbar',
         nonBillable: 'Nicht abrechenbar',
@@ -1657,7 +1657,7 @@ const translations: TranslationDeepObject<typeof en> = {
         },
         correctRateError: 'Beheben Sie den Kursfehler und versuchen Sie es erneut.',
         AskToExplain: `. <a href="${CONST.CONCIERGE_EXPLAIN_LINK_PATH}">Erklären<sparkles-icon/></a>`,
-        conciergeAutoMatchedVendor: ({vendorName}: {vendorName: string}) => `Concierge hat diese Ausgabe <strong>${vendorName}</strong> zugeordnet`,
+        conciergeAutoMatchedVendor: ({vendorName}: {vendorName: string}) => `Concierge hat diese Ausgabe mit <strong>${vendorName}</strong> abgeglichen`,
         duplicateNonDefaultWorkspacePerDiemError:
             'Sie können Per-Diem-Ausgaben nicht über mehrere Workspaces hinweg duplizieren, da sich die Sätze zwischen den Workspaces unterscheiden können.',
         rulesModifiedFields: {
diff --git a/src/languages/es.ts b/src/languages/es.ts
index 6257665a4a8..2b86e605c9c 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -1620,7 +1620,7 @@ const translations: TranslationDeepObject<typeof en> = {
         },
         correctRateError: 'Corrige el error de la tasa y vuelve a intentarlo.',
         AskToExplain: `. <a href="${CONST.CONCIERGE_EXPLAIN_LINK_PATH}">Explicar<sparkles-icon/></a>`,
-        conciergeAutoMatchedVendor: ({vendorName}: {vendorName: string}) => `Concierge asoció este gasto con <strong>${vendorName}</strong>`,
+        conciergeAutoMatchedVendor: ({vendorName}: {vendorName: string}) => `Concierge vinculó este gasto con <strong>${vendorName}</strong>`,
         rulesModifiedFields: {
             reimbursable: (value: boolean) => (value ? 'marcó el gasto como "reembolsable"' : 'marcó el gasto como "no reembolsable"'),
             billable: (value: boolean) => (value ? 'marcó el gasto como "facturable"' : 'marcó el gasto como "no facturable"'),
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 5d630887a5b..a21a491cca3 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -1663,7 +1663,7 @@ const translations: TranslationDeepObject<typeof en> = {
         },
         correctRateError: 'Corrigez l’erreur de taux et réessayez.',
         AskToExplain: `. <a href="${CONST.CONCIERGE_EXPLAIN_LINK_PATH}">Expliquer<sparkles-icon/></a>`,
-        conciergeAutoMatchedVendor: ({vendorName}: {vendorName: string}) => `Concierge a associé cette dépense au fournisseur <strong>${vendorName}</strong>`,
+        conciergeAutoMatchedVendor: ({vendorName}: {vendorName: string}) => `Concierge a fait correspondre cette dépense à <strong>${vendorName}</strong>`,
         duplicateNonDefaultWorkspacePerDiemError:
             'Vous ne pouvez pas dupliquer les indemnités journalières entre plusieurs espaces de travail, car les taux peuvent différer d’un espace de travail à l’autre.',
         rulesModifiedFields: {
diff --git a/src/languages/it.ts b/src/languages/it.ts
index f4336fa77d4..f379a8f5e47 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -1656,7 +1656,7 @@ const translations: TranslationDeepObject<typeof en> = {
         },
         correctRateError: "Correggi l'errore di tariffa e riprova.",
         AskToExplain: `. <a href="${CONST.CONCIERGE_EXPLAIN_LINK_PATH}">Spiega<sparkles-icon/></a>`,
-        conciergeAutoMatchedVendor: ({vendorName}: {vendorName: string}) => `Concierge ha associato questa spesa al fornitore <strong>${vendorName}</strong>`,
+        conciergeAutoMatchedVendor: ({vendorName}: {vendorName: string}) => `Concierge ha abbinato questa spesa a <strong>${vendorName}</strong>`,
         duplicateNonDefaultWorkspacePerDiemError: 'Non puoi duplicare le spese di diaria tra diversi spazi di lavoro perché le tariffe potrebbero essere diverse tra gli spazi di lavoro.',
         rulesModifiedFields: {
             reimbursable: (value: boolean) => (value ? 'ha contrassegnato la spesa come "rimborsabile"' : 'ha contrassegnato la spesa come "non rimborsabile"'),
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index ba954497372..faf0014237d 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -314,7 +314,7 @@ const translations: TranslationDeepObject<typeof en> = {
         merchant: '加盟店',
         change: '変更',
         category: 'カテゴリ',
-        vendor: 'ベンダー',
+        vendor: '仕入先',
         report: 'レポート',
         billable: '請求可能',
         nonBillable: '請求不可',
@@ -1637,7 +1637,7 @@ const translations: TranslationDeepObject<typeof en> = {
         },
         correctRateError: 'レートのエラーを修正して、もう一度お試しください。',
         AskToExplain: `・<a href="${CONST.CONCIERGE_EXPLAIN_LINK_PATH}">説明<sparkles-icon/></a>`,
-        conciergeAutoMatchedVendor: ({vendorName}: {vendorName: string}) => `Concierge がこの経費を <strong>${vendorName}</strong> に一致させました`,
+        conciergeAutoMatchedVendor: ({vendorName}: {vendorName: string}) => `Concierge がこの経費を<strong>${vendorName}</strong>にマッチしました`,
         duplicateNonDefaultWorkspacePerDiemError: 'ワークスペースごとに日当レートが異なる場合があるため、日当経費をワークスペース間で複製することはできません。',
         rulesModifiedFields: {
             reimbursable: (value: boolean) => (value ? '経費を「精算対象」に指定しました' : '経費を「精算対象外」にマークしました'),
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index d005d8705aa..80b1356b258 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -1650,7 +1650,7 @@ const translations: TranslationDeepObject<typeof en> = {
         },
         correctRateError: 'Corrija o erro de taxa e tente novamente.',
         AskToExplain: `. <a href="${CONST.CONCIERGE_EXPLAIN_LINK_PATH}">Explicar<sparkles-icon/></a>`,
-        conciergeAutoMatchedVendor: ({vendorName}: {vendorName: string}) => `Concierge associou esta despesa ao fornecedor <strong>${vendorName}</strong>`,
+        conciergeAutoMatchedVendor: ({vendorName}: {vendorName: string}) => `Concierge associou essa despesa a <strong>${vendorName}</strong>`,
         duplicateNonDefaultWorkspacePerDiemError: 'Você não pode duplicar despesas de diárias entre espaços de trabalho porque as tarifas podem variar entre eles.',
         rulesModifiedFields: {
             reimbursable: (value: boolean) => (value ? 'marcou a despesa como "reembolsável"' : 'marcou a despesa como “não reembolsável”'),
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 141c6e4c991..d96fd62801f 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -1602,7 +1602,7 @@ const translations: TranslationDeepObject<typeof en> = {
         },
         correctRateError: '修复费率错误后请重试。',
         AskToExplain: `。<a href="${CONST.CONCIERGE_EXPLAIN_LINK_PATH}">说明<sparkles-icon/></a>`,
-        conciergeAutoMatchedVendor: ({vendorName}: {vendorName: string}) => `Concierge 已将此支出匹配到<strong>${vendorName}</strong>`,
+        conciergeAutoMatchedVendor: ({vendorName}: {vendorName: string}) => `Concierge 已将此报销与 <strong>${vendorName}</strong> 匹配`,
         duplicateNonDefaultWorkspacePerDiemError: '您无法在不同工作区之间复制每日津贴报销,因为各工作区的补贴标准可能不同。',
         rulesModifiedFields: {
             reimbursable: (value: boolean) => (value ? '将该报销单标记为“可报销”' : '将该报销单标记为“不可报销”'),

Note

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

View workflow run

@codecov
Copy link
Copy Markdown

codecov Bot commented May 27, 2026

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/CONST/index.ts 93.84% <ø> (ø)
src/SCREENS.ts 100.00% <ø> (ø)
src/libs/Navigation/linkingConfig/config.ts 76.92% <ø> (ø)
...iou/request/step/withFullTransactionOrNotFound.tsx 95.65% <ø> (ø)
.../iou/request/step/withWritableReportOrNotFound.tsx 88.46% <ø> (ø)
...gation/AppNavigator/ModalStackNavigators/index.tsx 6.94% <0.00%> (-0.01%) ⬇️
...nbox/report/actionContents/ActionContentRouter.tsx 90.96% <33.33%> (-1.14%) ⬇️
...c/components/ReportActionItem/MoneyRequestView.tsx 75.26% <57.14%> (-0.35%) ⬇️
src/ROUTES.ts 18.14% <0.00%> (-0.07%) ⬇️
...actionContents/ConciergeAutoMatchVendorContent.tsx 11.11% <11.11%> (ø)
... and 1 more
... and 8 files with indirect coverage changes

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.

2 participants