Skip to content

Conversation

@cristipaval
Copy link
Contributor

@cristipaval cristipaval commented Jan 27, 2026

Explanation of Change

Fixed Issues

$ #80396
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 27, 2026
@OSBotify
Copy link
Contributor

🦜 Polyglot Parrot! 🦜

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

View the translation diff
diff --git a/src/languages/de.ts b/src/languages/de.ts
index 6c88f168..6fe752b8 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -638,6 +638,7 @@ const translations: TranslationDeepObject<typeof en> = {
         duplicateExpense: 'Doppelte Ausgabe',
         newFeature: 'Neue Funktion',
         month: 'Monat',
+        week: 'Woche',
     },
     supportalNoAccess: {
         title: 'Nicht so schnell',
@@ -6956,6 +6957,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.MONTH]: 'Monat',
+                [CONST.SEARCH.GROUP_BY.WEEK]: 'Woche',
             },
             feed: 'Feed',
             withdrawalType: {
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 7f08b053..d2f21ef9 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -640,6 +640,7 @@ const translations: TranslationDeepObject<typeof en> = {
         duplicateExpense: 'Note de frais en double',
         newFeature: 'Nouvelle fonctionnalité',
         month: 'Mois',
+        week: 'Semaine',
     },
     supportalNoAccess: {
         title: 'Pas si vite',
@@ -6967,6 +6968,7 @@ Exigez des informations de dépense comme les reçus et les descriptions, défin
                 [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'ID de retrait',
                 [CONST.SEARCH.GROUP_BY.CATEGORY]: 'Catégorie',
                 [CONST.SEARCH.GROUP_BY.MONTH]: 'Mois',
+                [CONST.SEARCH.GROUP_BY.WEEK]: 'Semaine',
             },
             feed: 'Flux',
             withdrawalType: {
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 7525885d..52b6b8ce 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -639,6 +639,7 @@ const translations: TranslationDeepObject<typeof en> = {
         duplicateExpense: 'Spesa duplicata',
         newFeature: 'Nuova funzionalità',
         month: 'Mese',
+        week: 'Settimana',
     },
     supportalNoAccess: {
         title: 'Non così in fretta',
@@ -6945,6 +6946,7 @@ Richiedi dettagli di spesa come ricevute e descrizioni, imposta limiti e valori
                 [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'ID prelievo', //_/\__/_/  \_,_/\__/\__/\_,_/
                 [CONST.SEARCH.GROUP_BY.CATEGORY]: 'Categoria',
                 [CONST.SEARCH.GROUP_BY.MONTH]: 'Mese',
+                [CONST.SEARCH.GROUP_BY.WEEK]: 'Settimana',
             },
             feed: 'Feed',
             withdrawalType: {
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 43f10ab5..789bba5b 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -638,6 +638,7 @@ const translations: TranslationDeepObject<typeof en> = {
         duplicateExpense: '重複した経費',
         newFeature: '新機能',
         month: '月',
+        week: '週',
     },
     supportalNoAccess: {
         title: 'ちょっと待ってください',
@@ -6882,9 +6883,10 @@ ${reportName}
             groupBy: {
                 [CONST.SEARCH.GROUP_BY.FROM]: '差出人',
                 [CONST.SEARCH.GROUP_BY.CARD]: 'カード',
-                [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: '出金ID',
+                [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: '出金 ID',
                 [CONST.SEARCH.GROUP_BY.CATEGORY]: 'カテゴリ',
                 [CONST.SEARCH.GROUP_BY.MONTH]: '月',
+                [CONST.SEARCH.GROUP_BY.WEEK]: '週',
             },
             feed: 'フィード',
             withdrawalType: {
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 5289966a..900a0d20 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -639,6 +639,7 @@ const translations: TranslationDeepObject<typeof en> = {
         duplicateExpense: 'Dubbele uitgave',
         newFeature: 'Nieuwe functie',
         month: 'Maand',
+        week: 'Week',
     },
     supportalNoAccess: {
         title: 'Niet zo snel',
@@ -6927,6 +6928,7 @@ Vraag verplichte uitgavedetails zoals bonnetjes en beschrijvingen, stel limieten
                 [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'Opname-ID',
                 [CONST.SEARCH.GROUP_BY.CATEGORY]: 'Categorie',
                 [CONST.SEARCH.GROUP_BY.MONTH]: 'Maand',
+                [CONST.SEARCH.GROUP_BY.WEEK]: 'Week',
             },
             feed: 'Feed',
             withdrawalType: {
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index a3772656..307f5200 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -639,6 +639,7 @@ const translations: TranslationDeepObject<typeof en> = {
         duplicateExpense: 'Zduplikowany wydatek',
         newFeature: 'Nowa funkcja',
         month: 'Miesiąc',
+        week: 'Tydzień',
     },
     supportalNoAccess: {
         title: 'Nie tak szybko',
@@ -6917,6 +6918,7 @@ Wymagaj szczegółów wydatków, takich jak paragony i opisy, ustawiaj limity i
                 [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'ID wypłaty',
                 [CONST.SEARCH.GROUP_BY.CATEGORY]: 'Kategoria',
                 [CONST.SEARCH.GROUP_BY.MONTH]: 'Miesiąc',
+                [CONST.SEARCH.GROUP_BY.WEEK]: 'Tydzień',
             },
             feed: 'Kanał',
             withdrawalType: {
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index ee7cd0e6..55737c17 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -638,6 +638,7 @@ const translations: TranslationDeepObject<typeof en> = {
         duplicateExpense: 'Despesa duplicada',
         newFeature: 'Novo recurso',
         month: 'Mês',
+        week: 'Semana',
     },
     supportalNoAccess: {
         title: 'Não tão rápido',
@@ -6915,9 +6916,10 @@ 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 de retirada',
+                [CONST.SEARCH.GROUP_BY.WITHDRAWAL_ID]: 'ID de saque',
                 [CONST.SEARCH.GROUP_BY.CATEGORY]: 'Categoria',
                 [CONST.SEARCH.GROUP_BY.MONTH]: 'Mês',
+                [CONST.SEARCH.GROUP_BY.WEEK]: 'Semana',
             },
             feed: 'Feed',
             withdrawalType: {
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index ee322f52..e70328a2 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -635,6 +635,7 @@ const translations: TranslationDeepObject<typeof en> = {
         duplicateExpense: '重复报销',
         newFeature: '新功能',
         month: '月',
+        week: '周',
     },
     supportalNoAccess: {
         title: '先别急',
@@ -6760,11 +6761,13 @@ ${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.WITHDRAWAL_ID]: '提现编号',
                 [CONST.SEARCH.GROUP_BY.CATEGORY]: '类别',
                 [CONST.SEARCH.GROUP_BY.MONTH]: '月',
+                [CONST.SEARCH.GROUP_BY.WEEK]: '周',
             },
             feed: '动态',
             withdrawalType: {

Note

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

@codecov
Copy link

codecov bot commented Jan 28, 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% <ø> (ø)
...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/SearchUIUtils.ts 63.64% <34.69%> (-0.42%) ⬇️
src/libs/SearchParser/searchParser.js 74.54% <71.97%> (-0.68%) ⬇️
... and 1 more
... and 7 files with indirect coverage changes

@cristipaval cristipaval marked this pull request as ready for review January 28, 2026 01:37
@cristipaval cristipaval requested review from a team as code owners January 28, 2026 01:37
@melvin-bot melvin-bot bot requested review from JmillsExpensify and shubham1206agra and removed request for a team and JmillsExpensify January 28, 2026 01:37
@melvin-bot
Copy link

melvin-bot bot commented Jan 28, 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 the request for review from a team January 28, 2026 01:37
@github-actions
Copy link
Contributor

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

if (isGroupEntry(key)) {
const weekGroup = data[key];
// Check if this is a week group by checking for week property
if (!('week' in weekGroup)) {
Copy link
Contributor

Choose a reason for hiding this comment

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

❌ PERF-13 (docs)

DateUtils.getWeekDateRange(weekGroup.week) is called twice in the same loop iteration - once inside the if (queryJSON && weekGroup.week) block and again immediately after. The second call produces the same result as the first since weekGroup.week hasn't changed.

Move the first call outside the conditional and reuse the result:

const {start: weekStart, end: weekEnd} = DateUtils.getWeekDateRange(weekGroup.week);
let transactionsQueryJSON: SearchQueryJSON | undefined;
if (queryJSON && weekGroup.week) {
    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);
    transactionsQueryJSON = buildSearchQueryJSON(newQuery);
}
const formattedWeek = DateUtils.getFormattedDateRangeForSearch(weekStart, weekEnd);

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

if (isTransactionItem && item?.reportAction?.childReportID) {
const isFromSelfDM = item.reportID === CONST.REPORT.UNREPORTED_REPORT_ID;
const isFromOneTransactionReport = isOneTransactionReport(item.report);
if (isTransactionWeekGroupListItemType(item)) {
Copy link
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 logic for creating date range filters from a week group is duplicated in src/libs/SearchUIUtils.ts in the getWeekSections function (lines 2337-2350). The same pattern of filtering out DATE filters, calling getWeekDateRange, and building a new query appears in both places.

Consider extracting this into a shared utility function:

// In a shared utilities file or SearchUtils
function buildWeekDateRangeQuery(
    weekStartDate: string,
    baseQueryJSON: SearchQueryJSON
): SearchQueryJSON | undefined {
    const {start: weekStart, end: weekEnd} = DateUtils.getWeekDateRange(weekStartDate);
    const newFlatFilters = baseQueryJSON.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 = {...baseQueryJSON, groupBy: undefined, flatFilters: newFlatFilters};
    const newQuery = buildSearchQueryString(newQueryJSON);
    return buildSearchQueryJSON(newQuery);
}

// Then use it here:
const newQueryJSONWithHash = buildWeekDateRangeQuery(weekGroupItem.week, queryJSON);

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

@github-actions
Copy link
Contributor

@shawnborton
Copy link
Contributor

Looks pretty good from a design standpoint 👍

shawnborton
shawnborton previously approved these changes Jan 28, 2026
@shubham1206agra
Copy link
Contributor

@cristipaval Fix the conflicts please

@cristipaval
Copy link
Contributor Author

Thanks for reviewing, @shawnborton! 🙏

Conflicts are resolved, @shubham1206agra.

merchant: "asc",
month: "desc"
month: "desc",
week: "desc",
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
week: "desc",
week: "desc"

Minor change :)

[CONST.SEARCH.TABLE_COLUMNS.GROUP_WEEK]: (
<View
key={CONST.SEARCH.TABLE_COLUMNS.GROUP_WEEK}
style={StyleUtils.getReportTableColumnStyles(CONST.SEARCH.TABLE_COLUMNS.GROUP_WEEK)}
Copy link
Contributor

Choose a reason for hiding this comment

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

@cristipaval Please refactor to use the new component for DRY

[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 da saque',
Copy link
Contributor

Choose a reason for hiding this comment

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

@cristipaval Do we need this change?

Comment on lines -6805 to +6809
[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.WITHDRAWAL_ID]: '提现编号',
Copy link
Contributor

Choose a reason for hiding this comment

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

@cristipaval Do we need these changes?

Comment on lines +280 to +281
[CONST.SEARCH.TABLE_COLUMNS.GROUP_EXPENSES]: 'count' as const,
[CONST.SEARCH.TABLE_COLUMNS.GROUP_TOTAL]: 'total' as const,
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
[CONST.SEARCH.TABLE_COLUMNS.GROUP_EXPENSES]: 'count' as const,
[CONST.SEARCH.TABLE_COLUMNS.GROUP_TOTAL]: 'total' as const,
...transactionGroupBaseSortingProperties,

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