Skip to content

feat: Extend shift+click range selection to Search results and report transaction lists - #98130

Draft
TaduJR wants to merge 22 commits into
Expensify:mainfrom
TaduJR:feat/90539-shift-range-search
Draft

feat: Extend shift+click range selection to Search results and report transaction lists#98130
TaduJR wants to merge 22 commits into
Expensify:mainfrom
TaduJR:feat/90539-shift-range-search

Conversation

@TaduJR

@TaduJR TaduJR commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Shift+click now selects a range in the Search results for expenses and reports, and in the transaction list on a report. Click one row, hold Shift, click another, and everything between them is selected. It runs on the same shared logic that shipped in part 1, so it behaves the way it already does in the tables.

A few things worth knowing:

  • Group headers work as before. Clicking one selects or clears the whole group. If the group is open, a Shift+click after that narrows the selection to the rows you pick.
  • Select all followed by a Shift+click narrows the selection to the range you clicked. Rows in groups you have not opened yet have not loaded, so they stay selected.
  • In the Reports view, rows inside an expanded report still select one at a time. Only the report rows themselves take part in a range.

Fixed Issues

$ #90539
PROPOSAL: #90539 (comment)

Tests

Prerequisite: You need a workspace with at least 10 expenses across 3 or more categories, and at least 3 reports that each contain several expenses.

1. Expenses list

  1. Go to Search/Spend, open the Expenses tab, and set Group by to none.
  2. Click the checkbox on the 2nd expense. Verify only that expense is checked.
  3. Hold Shift and click the checkbox on the 6th expense. Verify expenses 2 through 6 are all checked.
  4. Hold Shift and click the 4th expense. Verify the selection shrinks to 2 through 4, and 5 and 6 are now unchecked.
  5. Hold Shift and click the 8th expense. Verify expenses 2 through 8 are checked.
  6. Clear the selection, click the checkbox at the top of the list to select everything, then hold Shift and click the 3rd expense. Verify only expenses 1 through 3 stay checked.

2. Grouped expenses

  1. In the Expenses tab, set Group by to Category, then open the first two groups.
  2. Click the checkbox on the first expense in group 1, then hold Shift and click an expense in group 2. Verify every expense between the two is checked, across both groups, and the group headers update to match.
  3. Hold Shift and click an earlier expense in group 1. Verify the selection shrinks so only the expenses between your first click and this one stay checked.
  4. Open group 3 and click its header checkbox. Verify every expense in that group is checked.
  5. Hold Shift and click the 2nd expense in group 3. Verify only the first two expenses of that group stay checked.
  6. Close group 2 and open it again straight away, before the closing animation finishes. Click an expense above it, then hold Shift and click an expense below it. Verify the expenses inside group 2 are checked along with the rest.

3. Reports tab

  1. Go to Search/Spend and open the Reports tab.
  2. Click the checkbox on report 2, then hold Shift and click report 5. Verify reports 2 through 5 are checked.
  3. Clear the selection, then click the checkbox on report 6.
  4. Open report 8 and click the checkbox on one expense inside it. Verify that expense is checked and report 6 is still checked.
  5. Hold Shift and click report 9. Verify reports 6 through 9 are checked, and reports 1 through 5 are still unchecked.
  6. Inside an open report, hold Shift and click a second expense. Verify expenses inside a report are still selected one at a time; Shift does not select a stretch of them.

4. Expenses on a report

  1. Open a report that has at least 6 expenses.
  2. Click the checkbox on the 2nd expense, then hold Shift and click the 5th. Verify expenses 2 through 5 are checked.
  3. Hold Shift and click the 3rd expense. Verify the selection shrinks to 2 and 3.
  4. Group the report's expenses by Category, click a group header checkbox, then hold Shift and click the 2nd expense in that group. Verify the whole group checks first, then the selection narrows to the first two expenses.
  • Verify that no errors appear in the JS console

Offline tests

Same as tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."
Same as tests

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
    • MacOS: Desktop
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I verified there are no new alerts related to the canBeMissing param for useOnyx
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
Mac-Chrome.mp4

@TaduJR
TaduJR requested review from a team as code owners August 10, 2026 11:52
@melvin-bot
melvin-bot Bot requested a review from situchan August 10, 2026 11:52
@melvin-bot

melvin-bot Bot commented Aug 10, 2026

Copy link
Copy Markdown

@situchan 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 a team, joekaufmanexpensify and stitesExpensify and removed request for a team August 10, 2026 11:52
@melvin-bot

melvin-bot Bot commented Aug 10, 2026

Copy link
Copy Markdown

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

@TaduJR
TaduJR marked this pull request as draft August 10, 2026 11:53
@codecov

codecov Bot commented Aug 10, 2026

Copy link
Copy Markdown

Codecov Report

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

Files with missing lines Coverage Δ
...stReportView/MoneyRequestReportTransactionItem.tsx 0.00% <ø> (ø)
src/components/Search/SearchContext.tsx 100.00% <100.00%> (ø)
...rch/SearchList/ListItem/GroupChildrenContainer.tsx 0.00% <ø> (ø)
...h/SearchList/ListItem/TransactionGroupListItem.tsx 77.08% <100.00%> (+0.50%) ⬆️
src/components/Search/SearchList/ListItem/types.ts 100.00% <ø> (ø)
.../ListItem/useRegisterGroupChildrenForShiftRange.ts 100.00% <100.00%> (ø)
src/components/Search/SearchSelectionProvider.tsx 74.28% <100.00%> (+1.01%) ⬆️
src/components/Search/index.tsx 49.65% <ø> (ø)
src/hooks/useShiftRangeSelection.ts 98.01% <100.00%> (+0.25%) ⬆️
src/libs/SearchUIUtils.ts 66.58% <100.00%> (+0.59%) ⬆️
... and 13 more
... and 8 files with indirect coverage changes

Comment thread src/components/MoneyRequestReportView/MoneyRequestReportTransactionList.tsx Outdated
Comment thread src/components/Search/selectionBuilders.ts Outdated
Comment thread src/components/Search/SearchList/ListItem/TransactionGroupListItem.tsx Outdated
Comment thread src/components/Search/SearchList/ListItem/useGroupChildrenForShiftRange.ts Outdated
Comment thread src/components/Search/SearchWriteActionsProvider.tsx
TaduJR added 2 commits August 10, 2026 15:16
…shift-range-search

# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
@TaduJR

TaduJR commented Aug 10, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@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: adc86b1bf8

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

@TaduJR
TaduJR marked this pull request as ready for review August 10, 2026 12:58

@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: 62141034fb

ℹ️ 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 thread src/components/Search/SearchList/ListItem/useGroupChildrenForShiftRange.ts Outdated
@TaduJR

TaduJR commented Aug 10, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@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: 11cd7f08c1

ℹ️ 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 thread src/components/Search/SearchWriteActionsProvider.tsx

@joekaufmanexpensify joekaufmanexpensify left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Good for product

@TaduJR

TaduJR commented Aug 12, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@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: 46dcc486fe

ℹ️ 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 thread src/components/Search/SearchWriteActionsProvider.tsx Outdated
@TaduJR

TaduJR commented Aug 12, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@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: 9fae8b20d3

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

}
return updated;
},
{data: filteredData, totalSelectableItemsCount},

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Preserve all-matching selection in range updates

When an expense search is in “Select all matching” mode and the user Shift+clicks to shrink a visible range, this range path calls applySelection without the same shouldPreserveAllMatchingSelection/exclusion options used by normal row toggles. As soon as the range deselects any loaded row, applySelection clears areAllMatchingItemsSelected and drops the off-page matching expenses instead of recording those visible rows as exclusions, so bulk actions unexpectedly stop applying to the full matching result set. Please pass the same preservation options used by the single-row expense toggle here.

Useful? React with 👍 / 👎.

@TaduJR
TaduJR marked this pull request as draft August 12, 2026 11:25
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