Skip to content

Re-add missing CSV member import column mapping options with scroll fix#85575

Merged
francoisl merged 2 commits intomainfrom
claude-reAddMissingCsvImportColumnsWithScrollFix
Mar 18, 2026
Merged

Re-add missing CSV member import column mapping options with scroll fix#85575
francoisl merged 2 commits intomainfrom
claude-reAddMissingCsvImportColumnsWithScrollFix

Conversation

@MelvinBot
Copy link
Contributor

Explanation of Change

This PR re-implements the changes from PR #83823 (which was reverted via #84301) and also fixes the regression it introduced (#84276 — column mapping dropdown list not scrollable on mobile).

Original changes (from #83823):
The CSV member import flow (Workspace → Members → Import from spreadsheet) was missing 4 column mapping options that exist in Expensify Classic: Custom Field 1, Custom Field 2, Approval Limit, and Over Limit Forward To. This PR:

  1. Adds the 4 missing entries to the columnRoles array in ImportedMembersPage.tsx
  2. Extends the importMembers parsing logic to extract these columns from the spreadsheet data
  3. Extends the ImportedSpreadsheetMemberData type with the 4 optional fields
  4. Extends the PolicyMember type and importPolicyMembers function in Member.ts to include the new fields in the API payload
  5. Adds translation keys for "Approval limit" and "Over limit forward to" across all 10 language files

Regression fix (for #84276):
Adding 4 new options increased the dropdown from 5 to 9 items, exceeding mobile screen height. The ImportColumn component's ButtonWithDropdownMenu was missing the shouldPopoverUseScrollView prop, so the menu items were rendered in a non-scrollable <View>. This PR adds shouldPopoverUseScrollView={options.length >= CONST.DROPDOWN_SCROLL_THRESHOLD} to enable scrolling when there are 5+ options, following the established pattern used by SettlementButton, SearchBulkActionsButton, and MoneyReportHeaderKYCDropdown.

Fixed Issues

$ #83387
PROPOSAL: #83387 (comment)

Tests

  1. Go to Workspace → Members
  2. Click "Import from spreadsheet"
  3. Upload a CSV file with columns: Email, Role, Submit To, Forward To, Custom Field 1, Custom Field 2, Approval Limit, Over Limit Forward To
  4. Verify the column mapping dropdown now shows all 8 field options (plus Ignore)
  5. Tap on a column mapping dropdown on mobile — verify the list is scrollable
  6. Map each column to the appropriate field
  7. Click Import
  8. Verify the import completes successfully
  • Verify that no errors appear in the JS console

Offline tests

N/A — CSV import requires network to upload. The existing offline handling applies unchanged.

QA Steps

  1. Go to Workspace → Members in New Expensify
  2. Click "Import from spreadsheet"
  3. Upload a CSV file with headers: Email, Custom Field 1, Custom Field 2, Approval Limit, Over Limit Forward To
  4. Verify the column mapping dropdown includes Custom Field 1, Custom Field 2, Approval limit, and Over limit forward to as options
  5. On mobile (Android/iOS), verify the dropdown list is scrollable when tapping a column mapping dropdown
  6. Map columns and import
  7. Verify the imported data is reflected on member details
  • 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.

Screenshots/Videos

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

Re-implements the changes from PR #83823 which added Custom Field 1,
Custom Field 2, Approval Limit, and Over Limit Forward To to the
CSV member import column mapping dropdown.

Additionally fixes the regression from issue #84276 where the column
mapping dropdown list was not scrollable on mobile. The fix adds
shouldPopoverUseScrollView to the ButtonWithDropdownMenu in
ImportColumn.tsx, using the established DROPDOWN_SCROLL_THRESHOLD
pattern to enable scrolling when options >= 5.

Co-authored-by: truph01 <truph01@users.noreply.github.com>
@MelvinBot MelvinBot requested a review from a team March 17, 2026 17:56
@MelvinBot
Copy link
Contributor Author

I created this PR from an upstream branch since I don't have push access to your fork.

To take ownership of this branch and be able to push updates, run:

git remote add upstream https://github.com/Expensify/App.git
git fetch upstream claude-reAddMissingCsvImportColumnsWithScrollFix
git checkout -b claude-reAddMissingCsvImportColumnsWithScrollFix upstream/claude-reAddMissingCsvImportColumnsWithScrollFix
git push -u origin claude-reAddMissingCsvImportColumnsWithScrollFix

Then you can close this PR and open a new one from your fork.

@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 2d92304a..415295f0 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -492,7 +492,7 @@ const translations: TranslationDeepObject<typeof en> = {
         submitTo: 'Einreichen bei',
         forwardTo: 'Weiterleiten an',
         approvalLimit: 'Genehmigungslimit',
-        overLimitForwardTo: 'Weiterleiten bei Überschreitung',
+        overLimitForwardTo: 'Über Limit weiterleiten an',
         merge: 'Zusammenführen',
         none: 'Keine',
         unstableInternetConnection: 'Instabile Internetverbindung. Bitte überprüfe dein Netzwerk und versuche es erneut.',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 112540f1..5c543769 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -491,8 +491,8 @@ const translations: TranslationDeepObject<typeof en> = {
         headsUp: 'Attention !',
         submitTo: 'Soumettre à',
         forwardTo: 'Transférer à',
-        approvalLimit: "Limite d'approbation",
-        overLimitForwardTo: 'Transférer si dépassement de limite',
+        approvalLimit: 'Plafond d’approbation',
+        overLimitForwardTo: 'Transférer au-delà de la limite à',
         merge: 'Fusionner',
         none: 'Aucun',
         unstableInternetConnection: 'Connexion Internet instable. Veuillez vérifier votre réseau et réessayer.',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 401719c6..71dc4463 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -492,7 +492,7 @@ const translations: TranslationDeepObject<typeof en> = {
         submitTo: 'Invia a',
         forwardTo: 'Inoltra a',
         approvalLimit: 'Limite di approvazione',
-        overLimitForwardTo: 'Inoltra se supera il limite',
+        overLimitForwardTo: 'Inoltra eccedenza a',
         merge: 'Unisci',
         none: 'Nessuno',
         unstableInternetConnection: 'Connessione Internet instabile. Controlla la rete e riprova.',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index a41e9d58..e8482867 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -491,7 +491,7 @@ const translations: TranslationDeepObject<typeof en> = {
         submitTo: '提出先',
         forwardTo: '転送先',
         approvalLimit: '承認限度額',
-        overLimitForwardTo: '限度額超過時の転送先',
+        overLimitForwardTo: '限度超過時の転送先',
         merge: 'マージ',
         none: 'なし',
         unstableInternetConnection: 'インターネット接続が不安定です。ネットワークを確認して、もう一度お試しください。',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 2e3a1a10..7e1206b6 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -490,8 +490,8 @@ const translations: TranslationDeepObject<typeof en> = {
         headsUp: 'Let op!',
         submitTo: 'Indienen bij',
         forwardTo: 'Doorsturen naar',
-        approvalLimit: 'Goedkeuringslimiet',
-        overLimitForwardTo: 'Doorsturen bij overschrijding limiet',
+        approvalLimit: 'Autorisatielimiet',
+        overLimitForwardTo: 'Doorsturen bij overschrijding limiet naar',
         merge: 'Samenvoegen',
         none: 'Geen',
         unstableInternetConnection: 'Onstabiele internetverbinding. Controleer je netwerk en probeer het opnieuw.',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index c5dfdeed..b59732d6 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -490,8 +490,8 @@ const translations: TranslationDeepObject<typeof en> = {
         headsUp: 'Uwaga!',
         submitTo: 'Przekaż do',
         forwardTo: 'Przekaż do',
-        approvalLimit: 'Limit zatwierdzenia',
-        overLimitForwardTo: 'Przekaż przy przekroczeniu limitu',
+        approvalLimit: 'Limit zatwierdzania',
+        overLimitForwardTo: 'Przekaż powyżej limitu do',
         merge: 'Scal',
         none: 'Brak',
         unstableInternetConnection: 'Niestabilne połączenie internetowe. Sprawdź swoją sieć i spróbuj ponownie.',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 5f657ba3..75811523 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -490,7 +490,7 @@ const translations: TranslationDeepObject<typeof en> = {
         submitTo: 'Enviar para',
         forwardTo: 'Encaminhar para',
         approvalLimit: 'Limite de aprovação',
-        overLimitForwardTo: 'Encaminhar se exceder o limite',
+        overLimitForwardTo: 'Encaminhar excedente para',
         merge: 'Mesclar',
         none: 'Nenhum',
         unstableInternetConnection: 'Conexão de internet instável. Verifique sua rede e tente novamente.',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 970f0055..c31d7176 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -487,7 +487,7 @@ const translations: TranslationDeepObject<typeof en> = {
         submitTo: '提交给',
         forwardTo: '转发至',
         approvalLimit: '审批限额',
-        overLimitForwardTo: '超出限额时转发至',
+        overLimitForwardTo: '超限转发至',
         merge: '合并',
         none: '无',
         unstableInternetConnection: '网络连接不稳定。请检查您的网络后重试。',

Note

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

View workflow run

@MelvinBot
Copy link
Contributor Author

The failing check (build (Debug, true)) is unrelated to this PR's changes.

Analysis: The Android build failed because the Grails Maven repository (repo.grails.org) returned a 520 server error, causing Gradle to disable the repository and fail all dependency resolution (guava, javax.inject, and 164 others). This is a transient infrastructure issue.

Evidence: This PR only modifies TypeScript files, language files, and cspell.json — none of which affect Android Gradle dependency resolution. The error is:

Could not HEAD 'https://repo.grails.org/grails/core/javax/inject/javax.inject/1/javax.inject-1.pom'. Received status code 520 from server

Re-running the failed job should resolve this.

@codecov
Copy link

codecov bot commented Mar 17, 2026

Codecov Report

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

Files with missing lines Coverage Δ
src/components/ImportColumn.tsx 0.00% <ø> (ø)
src/libs/actions/Policy/Member.ts 73.00% <100.00%> (+0.93%) ⬆️
...rc/pages/workspace/members/ImportedMembersPage.tsx 0.00% <0.00%> (ø)
... and 7 files with indirect coverage changes

@trjExpensify
Copy link
Contributor

@truph01 please get this into review today. Customers are asking about this: https://expensify.slack.com/archives/C049HHMV9SM/p1773837348549279?thread_ts=1771946601.379139&cid=C049HHMV9SM

@truph01
Copy link
Contributor

truph01 commented Mar 18, 2026

@MelvinBot Please merge main, then mark this PR as ready for review.

…vImportColumnsWithScrollFix

Co-authored-by: truph01 <truph01@users.noreply.github.com>
@MelvinBot MelvinBot marked this pull request as ready for review March 18, 2026 13:22
@MelvinBot MelvinBot requested a review from a team as a code owner March 18, 2026 13:22
@MelvinBot
Copy link
Contributor Author

Done! Merged main into this branch (no conflicts) and marked the PR as ready for review.

@melvin-bot melvin-bot bot requested review from heyjennahay and truph01 and removed request for a team March 18, 2026 13:22
@melvin-bot
Copy link

melvin-bot bot commented Mar 18, 2026

@truph01 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 March 18, 2026 13:22
@trjExpensify trjExpensify requested review from trjExpensify and removed request for heyjennahay March 18, 2026 13:38
Copy link
Contributor

@trjExpensify trjExpensify left a comment

Choose a reason for hiding this comment

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

Re-introducing an agreed product change with a bug fix. 👍

@truph01
Copy link
Contributor

truph01 commented Mar 18, 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
  • 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 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
Screen.Recording.2026-03-19.at.01.17.43.mov
iOS: HybridApp
Screen.Recording.2026-03-19.at.01.20.34.mov
iOS: mWeb Safari
Screen.Recording.2026-03-19.at.01.19.38.mov
MacOS: Chrome / Safari
Screen.Recording.2026-03-19.at.01.13.40.mov

@melvin-bot
Copy link

melvin-bot bot commented Mar 18, 2026

We did not find an internal engineer to review this PR, trying to assign a random engineer to #83387 as well as to this PR... Please reach out for help on Slack if no one gets assigned!

@melvin-bot melvin-bot bot requested a review from francoisl March 18, 2026 18:37
"Tele",
"Teleproduction",
"testflight",
"THRESHHOLD",
Copy link
Contributor

Choose a reason for hiding this comment

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

@MelvinBot I see there's only 1 usage of this misspelled word outside of what this PR introduces – can you instead rename REPORT_THRESHHOLD to REPORT_THRESHOLD in CONST/index.ts, then update everywhere it's used, and remove it from here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good catch on the typo! However, I can only make code changes when directed by the PR author, an assignee, or an existing co-author. truph01 — should I implement this rename (REPORT_THRESHHOLDREPORT_THRESHOLD in CONST/index.ts + all usages, and remove it from cspell.json)?

Copy link
Contributor

Choose a reason for hiding this comment

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

Eh this is a minor nitpick and truph01 is offline, I'll merge as is now and do a follow-up PR for the typo so we can keep this moving.

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 online here

Copy link
Contributor

Choose a reason for hiding this comment

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

Haha too late but it's all right

@francoisl francoisl merged commit fc00e89 into main Mar 18, 2026
45 of 46 checks passed
@francoisl francoisl deleted the claude-reAddMissingCsvImportColumnsWithScrollFix branch March 18, 2026 21:15
@github-actions
Copy link
Contributor

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

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

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