Skip to content

Add support for groupBy week in Search - v2#80833

Merged
lakchote merged 3 commits intomainfrom
revert-80824-revert-80684-cristi_support-groupByWeek
Jan 29, 2026
Merged

Add support for groupBy week in Search - v2#80833
lakchote merged 3 commits intomainfrom
revert-80824-revert-80684-cristi_support-groupByWeek

Conversation

@cristipaval
Copy link
Copy Markdown
Contributor

@cristipaval cristipaval commented Jan 29, 2026

Explanation of Change

Adding groyp by week again after being reverted

Fixed Issues

$ #80396
$ #80814
$ #80818

PROPOSAL:

Tests

Tests

Prerequisites:

  • Ensure you have expenses with dates spanning multiple weeks (e.g., expenses from different weeks in January, February, March)
  • Ensure you have expenses from different days of the week, especially Sunday (critical for week grouping)
  • Ensure you have expenses from different years if testing across year boundaries

Test 1: Access Group by Week via Advanced Filters

  1. Open the app and navigate to the Reports page
  2. Go to Expense Section
  3. Tap the filter in the search header
  4. Tap on "Group by" option
  5. Verify "Week" appears in the list of group by options
  6. Select "Week"
  7. Tap "Save"
  8. Verify expenses are now grouped by week with headers showing:
    • Week date range (e.g., "Jan 25 - Jan 31, 2026", "Feb 1 - Feb 7, 2026")
    • Number of expenses in that week
    • Total amount for that week

Test 2: Verify Week Grouping Display (Large Screen)

  1. Open the app on desktop/web or tablet in landscape mode
  2. Go to Expense Section
  3. Navigate to Search and apply groupBy:week filter
  4. Verify the table header shows: Week icon | Week | Expenses | Total
  5. Verify each week row displays the calendar icon, week date range (e.g., "Jan 25 - Jan 31, 2026"), expense count, and total amount
  6. Verify columns are properly aligned between header and rows

Test 3: Verify Week Grouping Display (Small Screen)

  1. Open the app on mobile device
  2. Go to Expense Section
  3. Navigate to Search and apply groupBy:week filter
  4. Verify each week shows the calendar icon, week date range, and total amount
  5. Tap the expand arrow on a week row
  6. Verify the individual transactions within that week are displayed

Test 4: Verify Week Grouping Across Multiple Weeks

  1. Create expenses with dates spanning at least 3 different weeks
  2. Go to Expense Section
  3. Navigate to Search with groupBy:week
  4. Verify expenses are grouped into separate week sections
  5. Verify each week section shows the correct week date range
  6. Verify transactions appear only in their respective week groups

Test 5: Verify Week Expand/Collapse

  1. Navigate to Search with groupBy:week applied
  2. Tap/click on a week row (e.g., "Jan 25 - Jan 31, 2026")
  3. Verify the week row expands to show individual transactions within that week
  4. Tap/click on the week row again
  5. Verify the week row collapses to hide the transactions

Test 6: Verify Sorting

  1. Navigate to Search with groupBy:week
  2. Verify weeks are sorted chronologically (newest first by default, e.g., "Feb 1 - Feb 7, 2026", "Jan 25 - Jan 31, 2026", "Jan 18 - Jan 24, 2026")
  3. Click on the "Week" column header to sort
  4. Verify weeks sort chronologically (oldest first, then newest first on second click)
  5. Click on the "Total" column header
  6. Verify weeks sort by total amount (descending, then ascending on second click)

Test 7: Verify Multi-select Checkbox

  1. Navigate to Search with groupBy:week
  2. Enable selection mode (long press on mobile, or use bulk select)
  3. Tap the checkbox on a week header row
  4. Verify all transactions within that week become selected

Test 8: Verify Week Grouping Across Year Boundaries

  1. Create expenses with dates spanning December 28, 2025 - January 3, 2026 (a week that crosses year boundary)
  2. Go to Expense Section
  3. Navigate to Search with groupBy:week
  4. Verify expenses are grouped into a single week section showing cross-year date range (e.g., "Dec 28, 2025 - Jan 3, 2026")
  5. Verify transactions appear only in their respective week groups
  6. Verify weeks are sorted correctly across year boundaries (newest first)

Test 9: Verify Sunday Transaction Grouping (Critical Edge Case)

  1. Create an expense on Sunday, January 25, 2026
  2. Create expenses on other days of that week (Monday Jan 26, Wednesday Jan 28, Saturday Jan 31)
  3. Go to Expense Section
  4. Navigate to Search with groupBy:week
  5. Verify all expenses from Sunday Jan 25 through Saturday Jan 31 appear in the same week group
  6. Verify the week group shows date range starting with Sunday (e.g., "Jan 25 - Jan 31, 2026")
  7. Verify the Sunday transaction is NOT grouped into the previous week

Test 10: Verify Clicking Week Group Filters Transactions

  1. Navigate to Search with groupBy:week
  2. Click/tap on a week group header (e.g., "Jan 25 - Jan 31, 2026")
  3. Verify the search query updates to filter by that week's date range
  4. Verify groupBy is removed from the query
  5. Verify only transactions from that week are displayed as individual items (not grouped)
  6. Verify the date filter shows the week's start and end dates
  • Verify that no errors appear in the JS console

Offline tests

QA Steps

Same as steps.

  • 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 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.
  • I verified that similar component doesn't exist in the codebase
  • I verified that all props are defined accurately and each prop has a /** comment above it */
  • I verified that each file is named correctly
  • I verified that each component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • I verified that the only data being stored in component state is data necessary for rendering and nothing else
  • In component if we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
  • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
  • I verified that component internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
  • I verified that all JSX used for rendering exists in the render method
  • I verified that each component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
Screen.Recording.2026-01-27.at.17.34.11.mov

@cristipaval cristipaval self-assigned this Jan 29, 2026
@OSBotify
Copy link
Copy Markdown
Contributor

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff
diff --git a/src/languages/de.ts b/src/languages/de.ts
index 211b1dc7..651a0934 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -7001,7 +7001,7 @@ Fordere Spesendetails wie Belege und Beschreibungen an, lege Limits und Standard
                 [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'Auszahlungs-ID',
                 [CONST.SEARCH.GROUP_BY.CATEGORY]: 'Kategorie',
                 [CONST.SEARCH.GROUP_BY.MERCHANT]: 'Händler',
-                [CONST.SEARCH.GROUP_BY.TAG]: 'Stichwort',
+                [CONST.SEARCH.GROUP_BY.TAG]: 'Tag',
                 [CONST.SEARCH.GROUP_BY.MONTH]: 'Monat',
                 [CONST.SEARCH.GROUP_BY.WEEK]: 'Woche',
             },
diff --git a/src/languages/it.ts b/src/languages/it.ts
index dd80e98c..2263ad62 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -6989,7 +6989,7 @@ Richiedi dettagli di spesa come ricevute e descrizioni, imposta limiti e valori
                 [CONST.SEARCH.GROUP_BY.CARD]: 'Carta',
                 [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'ID prelievo', //_/\__/_/  \_,_/\__/\__/\_,_/
                 [CONST.SEARCH.GROUP_BY.CATEGORY]: 'Categoria',
-                [CONST.SEARCH.GROUP_BY.MERCHANT]: 'Commerciante',
+                [CONST.SEARCH.GROUP_BY.MERCHANT]: 'Esercente',
                 [CONST.SEARCH.GROUP_BY.TAG]: 'Etichetta',
                 [CONST.SEARCH.GROUP_BY.MONTH]: 'Mese',
                 [CONST.SEARCH.GROUP_BY.WEEK]: 'Settimana',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 5088ce87..f49e5e62 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -6925,10 +6925,10 @@ ${reportName}
             reimbursable: '精算対象',
             purchaseCurrency: '購入通貨',
             groupBy: {
-                [CONST.SEARCH.GROUP_BY.FROM]: '送信者',
+                [CONST.SEARCH.GROUP_BY.FROM]: '開始',
                 [CONST.SEARCH.GROUP_BY.CARD]: 'カード',
                 [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: '出金ID',
-                [CONST.SEARCH.GROUP_BY.CATEGORY]: 'カテゴリー',
+                [CONST.SEARCH.GROUP_BY.CATEGORY]: 'カテゴリ',
                 [CONST.SEARCH.GROUP_BY.MERCHANT]: '加盟店',
                 [CONST.SEARCH.GROUP_BY.TAG]: 'タグ',
                 [CONST.SEARCH.GROUP_BY.MONTH]: '月',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 8a8ccfda..202fad61 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -6972,7 +6972,7 @@ Vraag verplichte uitgavedetails zoals bonnetjes en beschrijvingen, stel limieten
                 [CONST.SEARCH.GROUP_BY.CARD]: 'Kaart',
                 [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'Opname-ID',
                 [CONST.SEARCH.GROUP_BY.CATEGORY]: 'Categorie',
-                [CONST.SEARCH.GROUP_BY.MERCHANT]: 'Verkoper',
+                [CONST.SEARCH.GROUP_BY.MERCHANT]: 'Handelaar',
                 [CONST.SEARCH.GROUP_BY.TAG]: 'Label',
                 [CONST.SEARCH.GROUP_BY.MONTH]: 'Maand',
                 [CONST.SEARCH.GROUP_BY.WEEK]: 'Week',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index a1994258..8bc1e2c6 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -6959,10 +6959,10 @@ Wymagaj szczegółów wydatków, takich jak paragony i opisy, ustawiaj limity i
             groupBy: {
                 [CONST.SEARCH.GROUP_BY.FROM]: 'Od',
                 [CONST.SEARCH.GROUP_BY.CARD]: 'Karta',
-                [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'ID wypłaty',
+                [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'Identyfikator wypłaty',
                 [CONST.SEARCH.GROUP_BY.CATEGORY]: 'Kategoria',
                 [CONST.SEARCH.GROUP_BY.MERCHANT]: 'Sprzedawca',
-                [CONST.SEARCH.GROUP_BY.TAG]: 'Etykieta',
+                [CONST.SEARCH.GROUP_BY.TAG]: 'Tag',
                 [CONST.SEARCH.GROUP_BY.MONTH]: 'Miesiąc',
                 [CONST.SEARCH.GROUP_BY.WEEK]: 'Tydzień',
             },
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index ba2cea47..523ed16c 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -6960,9 +6960,9 @@ Exija detalhes de despesas como recibos e descrições, defina limites e padrõe
             groupBy: {
                 [CONST.SEARCH.GROUP_BY.FROM]: 'De',
                 [CONST.SEARCH.GROUP_BY.CARD]: 'Cartão',
-                [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'ID da retirada',
+                [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'ID de saque',
                 [CONST.SEARCH.GROUP_BY.CATEGORY]: 'Categoria',
-                [CONST.SEARCH.GROUP_BY.MERCHANT]: 'Comerciante',
+                [CONST.SEARCH.GROUP_BY.MERCHANT]: 'Estabelecimento',
                 [CONST.SEARCH.GROUP_BY.TAG]: 'Etiqueta',
                 [CONST.SEARCH.GROUP_BY.MONTH]: 'Mês',
                 [CONST.SEARCH.GROUP_BY.WEEK]: 'Semana',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 692863b6..e714f0ff 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -6807,9 +6807,10 @@ ${reportName}
             groupBy: {
                 [CONST.SEARCH.GROUP_BY.FROM]: '来自',
                 [CONST.SEARCH.GROUP_BY.CARD]: '卡片',
+                //_/\__/_/  \_,_/\__/\__/\_,_/
                 [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: '提现 ID',
                 [CONST.SEARCH.GROUP_BY.CATEGORY]: '类别',
-                [CONST.SEARCH.GROUP_BY.MERCHANT]: '商家',
+                [CONST.SEARCH.GROUP_BY.MERCHANT]: '商户',
                 [CONST.SEARCH.GROUP_BY.TAG]: '标签',
                 [CONST.SEARCH.GROUP_BY.MONTH]: '月',
                 [CONST.SEARCH.GROUP_BY.WEEK]: '周',

Note

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

@codecov
Copy link
Copy Markdown

codecov bot commented Jan 29, 2026

Codecov Report

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

Files with missing lines Coverage Δ
src/CONST/index.ts 87.39% <ø> (ø)
...tionListWithSections/Search/BaseListItemHeader.tsx 100.00% <ø> (ø)
...stWithSections/Search/TransactionGroupListItem.tsx 71.69% <ø> (ø)
...tionListWithSections/Search/WeekListItemHeader.tsx 100.00% <100.00%> (ø)
src/libs/DateUtils.ts 63.21% <100.00%> (+1.08%) ⬆️
src/styles/utils/index.ts 49.56% <100.00%> (+0.07%) ⬆️
...ts/SelectionListWithSections/SearchTableHeader.tsx 5.79% <0.00%> (-0.18%) ⬇️
src/components/Search/SearchList/index.tsx 3.00% <0.00%> (-0.20%) ⬇️
src/components/Search/index.tsx 31.80% <0.00%> (-1.25%) ⬇️
src/libs/SearchParser/searchParser.js 73.87% <71.97%> (-0.67%) ⬇️
... and 2 more
... and 17 files with indirect coverage changes

@cristipaval cristipaval marked this pull request as ready for review January 29, 2026 01:36
@cristipaval cristipaval requested review from a team as code owners January 29, 2026 01:36
@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Jan 29, 2026

@shubham1206agra 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 request for a team January 29, 2026 01:36
// Extract the existing date filter to check for year-to-date or other date limits
const existingDateFilter = queryJSON.flatFilters.find((filter) => filter.key === CONST.SEARCH.SYNTAX_FILTER_KEYS.DATE);
const {start: weekStart, end: weekEnd} = adjustTimeRangeToDateFilters(DateUtils.getWeekDateRange(item.week), existingDateFilter);
const newFlatFilters = queryJSON.flatFilters.filter((filter) => filter.key !== CONST.SEARCH.SYNTAX_FILTER_KEYS.DATE);
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.

❌ CONSISTENCY-3 (docs)

This code block for creating date filters with week ranges is duplicated in src/libs/SearchUIUtils.ts (lines 2451-2463 in getWeekSections). The logic for filtering and rebuilding flatFilters with date range operators appears in two locations.

Impact: Duplicated logic increases maintenance burden and bug risk. If the filter creation logic needs to change, it must be updated in both places.

Suggested fix: Extract this logic into a reusable utility function:

function createDateFilterForWeek(
    queryJSON: SearchQueryJSON,
    week: string
): SearchQueryJSON | undefined {
    const existingDateFilter = queryJSON.flatFilters.find(
        (filter) => filter.key === CONST.SEARCH.SYNTAX_FILTER_KEYS.DATE
    );
    const {start: weekStart, end: weekEnd} = adjustTimeRangeToDateFilters(
        DateUtils.getWeekDateRange(week),
        existingDateFilter
    );
    
    const newFlatFilters = queryJSON.flatFilters.filter(
        (filter) => filter.key \!== CONST.SEARCH.SYNTAX_FILTER_KEYS.DATE
    );
    newFlatFilters.push({
        key: CONST.SEARCH.SYNTAX_FILTER_KEYS.DATE,
        filters: [
            {operator: CONST.SEARCH.SYNTAX_OPERATORS.GREATER_THAN_OR_EQUAL_TO, value: weekStart},
            {operator: CONST.SEARCH.SYNTAX_OPERATORS.LOWER_THAN_OR_EQUAL_TO, value: weekEnd},
        ],
    });
    
    const newQueryJSON: SearchQueryJSON = {
        ...queryJSON,
        groupBy: undefined,
        flatFilters: newFlatFilters
    };
    const newQuery = buildSearchQueryString(newQueryJSON);
    return buildSearchQueryJSON(newQuery);
}

Then use it in both locations instead of duplicating the logic.


Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

Copy link
Copy Markdown

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

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

@trjExpensify trjExpensify requested review from trjExpensify and removed request for joekaufmanexpensify January 29, 2026 02:20
Copy link
Copy Markdown
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.

Core Insights PR 👍

@shubham1206agra
Copy link
Copy Markdown
Contributor

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 there are no new alerts related to the canBeMissing param for useOnyx
  • 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
  • xIf 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

Screen.Recording.2026-01-28.at.11.27.38.PM.mov
Screen.Recording.2026-01-29.at.1.32.51.PM.mov

return Object.values(CONST.SEARCH.DATE_PRESETS).some((datePreset) => datePreset === value);
}

function adjustTimeRangeToDateFilters(timeRange: {start: string; end: string}, dateFilter: QueryFilters[0] | undefined): {start: string; end: string} {
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.

@cristipaval Follow up task. Please add tests for all these functions as it is really complex in nature.

@melvin-bot melvin-bot bot requested a review from MariaHCD January 29, 2026 08:14
@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Jan 29, 2026

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

Copy link
Copy Markdown
Contributor

@lakchote lakchote left a comment

Choose a reason for hiding this comment

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

LGTM

@lakchote lakchote merged commit eb7deee into main Jan 29, 2026
38 of 39 checks passed
@lakchote lakchote deleted the revert-80824-revert-80684-cristi_support-groupByWeek branch January 29, 2026 08:20
@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/lakchote in version: 9.3.11-16 🚀

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

@OSBotify
Copy link
Copy Markdown
Contributor

OSBotify commented Feb 5, 2026

🚀 Deployed to production by https://github.com/Julesssss in version: 9.3.12-1 🚀

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

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