Skip to content

Add Export current view - #93060

Merged
marcochavezf merged 8 commits into
mainfrom
rodrigo-export-curret-view-2
Jun 16, 2026
Merged

Add Export current view#93060
marcochavezf merged 8 commits into
mainfrom
rodrigo-export-curret-view-2

Conversation

@rlinoz

@rlinoz rlinoz commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

First attempt #90714 was reverted due to some backend issues, this is the second try.

Fixed Issues

$ #92314
$ https://github.com/Expensify/Expensify/issues/633210
PROPOSAL:

Tests

  1. Go to spend
  2. Edit the display columns
  3. Select some expenses > Export > Export current view
  4. Verify the CSV has all the columns being displayed
  5. Go to Reports
  6. Edit the display columns
  7. Select some reports > Export > Export current view
  8. Verify the CSV has all the columns being displayed
  • Verify that no errors appear in the JS console

Offline tests

QA Steps

  1. Go to spend
  2. Edit the display columns
  3. Select some expenses > Export > Export current view
  4. Verify the CSV has all the columns being displayed
  5. Go to Reports
  6. Edit the display columns
  7. Select some reports > Export > Export current view
  8. Verify the CSV has all the columns being displayed
  • 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

@rlinoz rlinoz self-assigned this Jun 9, 2026
@OSBotify

OSBotify commented Jun 9, 2026

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 e95e462a5b4..01a36aba1c1 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -9476,6 +9476,7 @@ Hier ist ein *Testbeleg*, um dir zu zeigen, wie es funktioniert:`,
         expenseLevelExport: 'Alle Daten – Ausgabenebene',
         exportInProgress: 'Export wird ausgeführt',
         conciergeWillSend: 'Concierge wird dir die Datei in Kürze senden.',
+        currentView: 'Aktuelle Ansicht exportieren',
     },
     exportDownload: {
         preparingTitle: 'Preparing download...',
diff --git a/src/languages/es.ts b/src/languages/es.ts
index cabeef3d992..9a6a5bbbe67 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -9635,6 +9635,7 @@ ${amount} para ${merchant} - ${date}`,
         expenseLevelExport: 'Todos los datos - a nivel de gasto',
         exportInProgress: 'Exportación en curso',
         conciergeWillSend: 'Concierge te enviará el archivo en breve.',
+        currentView: 'Exportar vista actual',
     },
     exportDownload: {
         preparingTitle: 'Preparando descarga...',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index fcdffae64dd..239f2652c2d 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -9508,6 +9508,7 @@ Voici un *reçu test* pour vous montrer comment ça fonctionne :`,
         expenseLevelExport: 'Toutes les données - niveau dépense',
         exportInProgress: 'Export en cours',
         conciergeWillSend: 'Concierge vous enverra le fichier sous peu.',
+        currentView: 'Exporter la vue actuelle',
     },
     exportDownload: {
         preparingTitle: 'Preparing download...',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index c45a5615b4b..854c1236f23 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -9464,6 +9464,7 @@ Ecco una *ricevuta di prova* per mostrarti come funziona:`,
         expenseLevelExport: 'Tutti i dati - livello spesa',
         exportInProgress: 'Esportazione in corso',
         conciergeWillSend: 'Concierge ti invierà il file a breve.',
+        currentView: 'Esporta vista corrente',
     },
     exportDownload: {
         preparingTitle: 'Preparing download...',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index d12c6a42ec5..8ab28f5313a 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -9342,6 +9342,7 @@ ${reportName}
         expenseLevelExport: 'すべてのデータ - 経費レベル',
         exportInProgress: 'エクスポート処理中',
         conciergeWillSend: 'Conciergeがまもなくファイルを送信します。',
+        currentView: '現在のビューをエクスポート',
     },
     exportDownload: {
         preparingTitle: 'Preparing download...',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index feafe70ce5f..d0759964c73 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -9431,6 +9431,7 @@ Hier is een *proefbon* om je te laten zien hoe het werkt:`,
         expenseLevelExport: 'Alle gegevens - uitgaveniveau',
         exportInProgress: 'Export bezig',
         conciergeWillSend: 'Concierge stuurt je het bestand zo meteen.',
+        currentView: 'Huidige weergave exporteren',
     },
     exportDownload: {
         preparingTitle: 'Preparing download...',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 977248589dd..df8a8d30010 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -9415,6 +9415,7 @@ Oto *paragon testowy*, żeby pokazać Ci, jak to działa:`,
         expenseLevelExport: 'Wszystkie dane – poziom wydatku',
         exportInProgress: 'Trwa eksport',
         conciergeWillSend: 'Concierge wkrótce wyśle Ci plik.',
+        currentView: 'Eksportuj bieżący widok',
     },
     exportDownload: {
         preparingTitle: 'Preparing download...',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index e498d8b8090..28646e5cde9 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -9423,6 +9423,7 @@ Aqui está um *comprovante de teste* para mostrar como funciona:`,
         expenseLevelExport: 'Todos os dados - nível de despesa',
         exportInProgress: 'Exportação em andamento',
         conciergeWillSend: 'O Concierge enviará o arquivo para você em breve.',
+        currentView: 'Exportar visão atual',
     },
     exportDownload: {
         preparingTitle: 'Preparing download...',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 49a40c86b0e..cfd99cecc68 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -9169,6 +9169,7 @@ ${reportName}
         expenseLevelExport: '所有数据 - 报销级别',
         exportInProgress: '导出进行中',
         conciergeWillSend: 'Concierge 将很快把文件发送给你。',
+        currentView: '导出当前视图',
     },
     exportDownload: {
         preparingTitle: 'Preparing download...',

Note

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

View workflow run

@rlinoz rlinoz changed the title Add Export current view [HOLD Auth#22119] Add Export current view Jun 10, 2026
rlinoz and others added 4 commits June 10, 2026 13:03
- Drop the narrowing `as SearchQueryJSON['columns']` assertion in
  getCSVExportParameters; serializeQueryJSONForBackend is generic and
  infers the column type, so the cast is unnecessary and pushed the file
  one over the eslint-seatbelt no-unsafe-type-assertion baseline.
- Mock getValidGroupBy/getColumnsToShow/getSearchColumnTranslationKey in
  useSearchBulkActionsDeleteTest so getExportOptions no longer throws.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@codecov

codecov Bot commented Jun 10, 2026

Copy link
Copy Markdown

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/libs/actions/Search.ts 34.86% <0.00%> (ø)
src/libs/SearchUIUtils.ts 64.16% <0.00%> (-0.22%) ⬇️
src/hooks/useSearchBulkActions.ts 49.28% <22.64%> (-0.35%) ⬇️
... and 42 files with indirect coverage changes

@rlinoz rlinoz changed the title [HOLD Auth#22119] Add Export current view Add Export current view Jun 11, 2026
@rlinoz
rlinoz requested a review from thesahindia June 11, 2026 12:52
@rlinoz
rlinoz marked this pull request as ready for review June 11, 2026 12:53
@rlinoz
rlinoz requested review from a team as code owners June 11, 2026 12:53
@melvin-bot
melvin-bot Bot requested review from heyjennahay and marcochavezf and removed request for a team June 11, 2026 12:53
@melvin-bot

melvin-bot Bot commented Jun 11, 2026

Copy link
Copy Markdown

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

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

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: 44951e2482

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/hooks/useSearchBulkActions.ts
@thesahindia

thesahindia commented Jun 13, 2026

Copy link
Copy Markdown
Member

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

Having issues with android build

Android: mWeb Chrome
Screen.Recording.2026-06-13.at.3.19.37.PM.mov
iOS: HybridApp
Screen.Recording.2026-06-13.at.1.44.58.PM.mov
iOS: mWeb Safari
Screen.Recording.2026-06-13.at.1.55.51.PM.mov
MacOS: Chrome / Safari
Screen.Recording.2026-06-13.at.10.01.51.AM.mov
Screen.Recording.2026-06-13.at.6.57.18.AM.mov
Screen.Recording.2026-06-13.at.6.38.18.AM.mov

@thesahindia thesahindia left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Looks good. I couldn't reproduce the previous issues.

@marcochavezf
marcochavezf merged commit 6f935f9 into main Jun 16, 2026
38 of 39 checks passed
@marcochavezf
marcochavezf deleted the rodrigo-export-curret-view-2 branch June 16, 2026 03:04
@github-actions

Copy link
Copy Markdown
Contributor

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

@OSBotify

Copy link
Copy Markdown
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
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/marcochavezf in version: 9.4.9-0 🚀

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

Bundle Size Analysis (Sentry):

@MelvinBot

Copy link
Copy Markdown
Contributor

Help site review

I reviewed the changes in this PR. They introduce a new Export current view option in the bulk Export menu on the Spend page (Search), which downloads a CSV matching the columns currently displayed (configured via Display > Edit columns) instead of a fixed template. The option appears on the ungrouped Expenses and Reports views and is hidden when a Group by filter is applied.

Help site changes are required, and they were already drafted when the first attempt (Expensify/App#90714) merged. Rather than open a duplicate, I've updated that existing draft to reference this PR (#90714 was reverted and re-landed here as this PR) and lifted the product HOLD now that the change has shipped:

📝 Draft help site PR: Expensify/App#92191

It updates three articles:

The PR is a draft, has the HelpDot label, and is assigned to you.

@rlinoz, please review the linked help site PR and confirm it reflects the current behavior. Then mark the linked help site PR Ready for review

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/puneetlath in version: 9.4.9-0 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor

🤖 I was unable to capture a live screenshot: browser verification runs in a CI environment where sign-in to dev NewDot is blocked (Cloudflare bot detection returns 429 on SignUpUser, and the transactional email provider rejects the throwaway aliases), so no authenticated session could be established to reach the Reports view.

I did confirm the feature is present at the code level on the merged commit (c8d6035):

"Export current view" is wired into the Reports Export menu. The Export dropdown is built in useSearchBulkActions.ts:

  • For a grouped search (Reports are grouped by report), the basic-export entry is relabeled to the "Current view" option — useSearchBulkActions.ts:1578.
  • For a non-grouped search, an explicit "Current view" option is added that calls handleExportCurrentView()useSearchBulkActions.ts:1587-1598.
  • The label resolves to the string Current viewen.ts:10072.
Why no screenshot / what was attempted

The app-web-tester attempted sign-in with several throwaway gmail +alias accounts. BeginSignIn succeeded but SignUpUser returned HTTP 429 with cf-mitigated: challenge (Cloudflare flagging the headless Chrome IP/user-agent), and one alias was pre-emptively rejected by Expensify's email provider ("temporarily suspended emails"). Without a signed-in session the Reports section and its Export toolbar are unreachable.

To get an actual on-web screenshot, this needs to be run against a pre-seeded/verified test account whose session is injected into the browser, or from an environment not blocked by Cloudflare on the account-creation endpoint.

Summary: ✅ The "Export current view" option is present in code for the Reports Export menu on the merged commit. ⚠️ I could not produce a live web screenshot or exercise the actual CSV export due to CI sign-in restrictions — a manual/QA pass on staging (per the PR's QA steps) is still needed to visually confirm it.

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