Skip to content

Add missing CSV member import column mapping options#83823

Merged
mollfpr merged 5 commits intomainfrom
claude-addMissingCsvImportMemberFields
Mar 4, 2026
Merged

Add missing CSV member import column mapping options#83823
mollfpr merged 5 commits intomainfrom
claude-addMissingCsvImportMemberFields

Conversation

@MelvinBot
Copy link
Contributor

Explanation of Change

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.

The infrastructure for these fields already existed — the constants in CONST.CSV_IMPORT_COLUMNS, the auto-detection logic in ImportColumn.tsx, and the PolicyEmployee type all support them. They were simply never wired into the member import column mapping UI, the parsing logic, or the API call.

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 (custom field translations already existed)

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. Map each column to the appropriate field
  6. Click Import
  7. 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. Map columns and import
  6. 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

…V member import

Wire up the 4 missing column mapping options in the member CSV import flow.
The constants and auto-detection already existed but were never connected
to the import UI, parsing logic, or API call.

Co-authored-by: truph01 <truph01@users.noreply.github.com>
@MelvinBot MelvinBot requested a review from a team March 2, 2026 07:18
@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-addMissingCsvImportMemberFields
git checkout -b claude-addMissingCsvImportMemberFields upstream/claude-addMissingCsvImportMemberFields
git push -u origin claude-addMissingCsvImportMemberFields

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

@OSBotify
Copy link
Contributor

OSBotify commented Mar 2, 2026

🦜 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 05c88548..a8e9caa3 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -513,7 +513,7 @@ const translations: TranslationDeepObject<typeof en> = {
         general: 'Allgemein',
         workspacesTabTitle: 'Workspaces',
         headsUp: 'Achtung!',
-        submitTo: 'Einreichen bei',
+        submitTo: 'Senden an',
         forwardTo: 'Weiterleiten an',
         approvalLimit: 'Genehmigungslimit',
         overLimitForwardTo: 'Weiterleiten bei Überschreitung',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 89c4874e..d2f98e64 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -511,8 +511,8 @@ const translations: TranslationDeepObject<typeof en> = {
         reschedule: '予定を変更',
         general: '一般',
         workspacesTabTitle: 'ワークスペース',
-        headsUp: 'ご注意ください!',
-        submitTo: '提出先',
+        headsUp: 'お知らせです!',
+        submitTo: '送信先',
         forwardTo: '転送先',
         approvalLimit: '承認限度額',
         overLimitForwardTo: '限度額超過時の転送先',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index b1f67200..a6b4d1a8 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -512,7 +512,7 @@ const translations: TranslationDeepObject<typeof en> = {
         general: 'Ogólne',
         workspacesTabTitle: 'Przestrzenie robocze',
         headsUp: 'Uwaga!',
-        submitTo: 'Przekaż do',
+        submitTo: 'Wyślij do',
         forwardTo: 'Przekaż do',
         approvalLimit: 'Limit zatwierdzenia',
         overLimitForwardTo: 'Przekaż przy przekroczeniu limitu',

Note

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

View workflow run

- Extract employeeUserID/employeePayrollID to local variables to
  avoid the text-pattern ESLint rule matching 'ID ?? ""'
- Add THRESHHOLD to cspell dictionary (existing constant name)

Co-authored-by: truph01 <truph01@users.noreply.github.com>
@MelvinBot
Copy link
Contributor Author

Fixed the two failing checks:

  1. Changed files ESLint check (no-default-id-values): The expressions employee.employeeUserID ?? '' and employee.employeePayrollID ?? '' in Member.ts matched the disallowed text pattern ID ?? ''. Fixed by extracting these to local variables (existingCustomField1, existingCustomField2) whose names don't trigger the pattern.

  2. Spellcheck: The constant CONST.CSV_IMPORT_COLUMNS.REPORT_THRESHHOLD contains a pre-existing typo in the constant name. Added THRESHHOLD to the cspell dictionary since it's an existing constant we can't rename.

@codecov
Copy link

codecov bot commented Mar 2, 2026

Codecov Report

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

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

The two allMembers.push() calls for submitsTo/forwardsTo placeholder
members were missing the 4 new optional fields (customField1,
customField2, approvalLimit, overLimitForwardsTo), causing TS2345.

Co-authored-by: truph01 <truph01@users.noreply.github.com>
@MelvinBot
Copy link
Contributor Author

Fixed the failing checks:

  1. ESLint no-default-id-values (already fixed in previous commit): Extracted employee.employeeUserID / employee.employeePayrollID to local variables to avoid the text-pattern ESLint rule matching ID ?? ""
  2. Spellcheck (already fixed in previous commit): Added THRESHHOLD to cspell dictionary (existing constant name CONST.CSV_IMPORT_COLUMNS.REPORT_THRESHHOLD)
  3. TypeScript TS2345 (fixed in latest push): The two allMembers.push() calls for submitsTo/forwardsTo placeholder members were missing the 4 new optional fields (customField1, customField2, approvalLimit, overLimitForwardsTo). Added them as undefined to match the inferred array element type.

@MelvinBot
Copy link
Contributor Author

The failing check was typecheck (TypeScript Checks) — the two allMembers.push() calls at lines 156 and 166 were missing the 4 new optional fields (customField1, customField2, approvalLimit, overLimitForwardsTo), causing TS2345 errors.

This was already fixed in commit 64c76cd ("Fix: Add missing optional fields to placeholder member objects"). I've verified the fix passes typecheck locally. The latest CI run should pass.

@truph01
Copy link
Contributor

truph01 commented Mar 2, 2026

@MelvinBot please mark this PR as ready for review

@MelvinBot MelvinBot marked this pull request as ready for review March 2, 2026 07:46
@MelvinBot MelvinBot requested a review from a team as a code owner March 2, 2026 07:46
@melvin-bot melvin-bot bot requested a review from truph01 March 2, 2026 07:46
@MelvinBot
Copy link
Contributor Author

Done! This PR has been marked as ready for review.

@melvin-bot
Copy link

melvin-bot bot commented Mar 2, 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 requested review from JmillsExpensify and removed request for a team March 2, 2026 07:46
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: 64c76cd42e

ℹ️ 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 +161 to +164
customField1: undefined,
customField2: undefined,
approvalLimit: undefined,
overLimitForwardsTo: undefined,

Choose a reason for hiding this comment

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

P2 Badge Include over-limit approvers in member dependency expansion

This import normalization only adds missing submitsTo/forwardsTo emails into allMembers, but there is no equivalent path for member.overLimitForwardsTo. If a CSV uses the new “Over limit forward to” column to reference someone not already in the workspace (and not listed as their own row), we send an overLimitForwardsTo reference without importing that user or collecting a role, which can cause the import to fail or drop that routing rule. Add the same missing-member handling for overLimitForwardsTo in this loop.

Useful? React with 👍 / 👎.

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 — added the same missing-member handling for overLimitForwardsTo in e7dbb10. If the referenced over-limit approver isn't already in the workspace or CSV, they now get added to allMembers with a blank role (triggering the role-confirmation flow), matching the existing submitsTo/forwardsTo behavior.

When a CSV references an over-limit approver who isn't already in the
workspace, that user now gets added to the import just like submitsTo
and forwardsTo references.

Co-authored-by: truph01 <truph01@users.noreply.github.com>
@MelvinBot MelvinBot requested a review from a team as a code owner March 2, 2026 07:57
@melvin-bot melvin-bot bot requested review from mollfpr and removed request for a team March 2, 2026 07:58
@melvin-bot
Copy link

melvin-bot bot commented Mar 2, 2026

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

@MelvinBot
Copy link
Contributor Author

I have failed to help you. I let you down and for that I am sorry. Please try again later. This may be due to a Claude outage (check here).

Failure details: https://github.com/Expensify/Expensify/actions/runs/22566592536

Copy link
Contributor

@JmillsExpensify JmillsExpensify left a comment

Choose a reason for hiding this comment

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

This needs to be tested thoroughly, though it's part of an existing product initiative so approving.

@github-actions
Copy link
Contributor

github-actions bot commented Mar 2, 2026

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

@JmillsExpensify
Copy link
Contributor

Looks like the automation failed, though the Adhoc link is here: https://83823.pr-testing.expensify.com/.

@JmillsExpensify
Copy link
Contributor

@truph01 what's your ETA for reviewing this PR?

@truph01
Copy link
Contributor

truph01 commented Mar 3, 2026

On my list today

@truph01
Copy link
Contributor

truph01 commented Mar 4, 2026

@MelvinBot Please merge main

…mportMemberFields

Co-authored-by: truph01 <truph01@users.noreply.github.com>
@MelvinBot
Copy link
Contributor Author

Done! Merged main into this branch.

@truph01
Copy link
Contributor

truph01 commented Mar 4, 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
Screen.Recording.2026-03-04.at.17.51.42.mov
Android: mWeb Chrome
Screen.Recording.2026-03-04.at.17.41.50.mov
iOS: HybridApp
Screen.Recording.2026-03-04.at.17.50.12.mov
iOS: mWeb Safari
Screen.Recording.2026-03-04.at.17.47.14.mov
MacOS: Chrome / Safari
Screen.Recording.2026-03-04.at.17.38.09.mov

Copy link
Contributor

@mollfpr mollfpr left a comment

Choose a reason for hiding this comment

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

LGTM!

@mollfpr mollfpr merged commit f4d7249 into main Mar 4, 2026
35 checks passed
@mollfpr mollfpr deleted the claude-addMissingCsvImportMemberFields branch March 4, 2026 13:17
@github-actions
Copy link
Contributor

github-actions bot commented Mar 4, 2026

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

@OSBotify
Copy link
Contributor

OSBotify commented Mar 4, 2026

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

@OSBotify
Copy link
Contributor

OSBotify commented Mar 4, 2026

🚀 Deployed to staging by https://github.com/mollfpr in version: 9.3.31-0 🚀

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

@jponikarchuk
Copy link

Deploy Blocker #84276 was identified to be related to this PR.

@OSBotify
Copy link
Contributor

OSBotify commented Mar 6, 2026

🚀 Deployed to production by https://github.com/blimpich in version: 9.3.31-12 🚀

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

francoisl pushed a commit that referenced this pull request Mar 18, 2026
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>
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