Skip to content

#2 - Update advanced filters button to open filters popover#91806

Open
bernhardoj wants to merge 22 commits into
Expensify:mainfrom
bernhardoj:feat/84877-update-filters-chip-to-open-filters-popup
Open

#2 - Update advanced filters button to open filters popover#91806
bernhardoj wants to merge 22 commits into
Expensify:mainfrom
bernhardoj:feat/84877-update-filters-chip-to-open-filters-popup

Conversation

@bernhardoj
Copy link
Copy Markdown
Contributor

Explanation of Change

Fixed Issues

$ #84877
PROPOSAL:

Tests

Same as QA Steps

  • Verify that no errors appear in the JS console

Offline tests

Same as QA Steps

QA Steps

Prerequisite: have a workspace with report fields

Web

  1. Go to the Spend page
  2. Press the Filters button
  3. Verify the advanced filter popover opens
  4. Hover over any filter
  5. For a selection-based filter, press any of the selections and verify that the filter is applied
  6. For a text input-based filter, enter anything, press Apply, and verify the filter is applied
  7. For a date-based filter, press Custom date or Custom range, apply the value, and verify the filter is applied
  8. For an amount-based filter, select any option and verify that a text input is shown below the selection
  9. Choose between and verify a greater than and less than text inputs are shown
  10. Apply any selection and value, and verify the filter is applied
  11. Open a report field filter, open any field and verify the filter is applied only after pressing the Apply button

mWeb, Android, iOS

  1. Go to the Spend page
  2. Press the Filters button
  3. Verify the advanced filter opens in full screen
  4. Verify there is an Apply button and there is no Reset button at the footer
  5. Press any filter
  6. Verify it shows the selected filter
  7. Set any value and press Apply
  8. Verify it goes back to the filter list
  9. Press Apply again and verify the filters are applied
  10. Press the Filters button
  11. Verify there is a Reset button
  12. Press Reset
  13. Verify the filter is reset
  • 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
    • 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
web.mp4

@bernhardoj bernhardoj requested review from a team as code owners May 27, 2026 08:56
@melvin-bot melvin-bot Bot requested review from aimane-chnaif and trjExpensify and removed request for a team May 27, 2026 08:56
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 27, 2026

@aimane-chnaif 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 May 27, 2026 08:56
Comment thread src/components/SafeTriangle/index.tsx
Comment thread src/components/Search/SearchList/BaseSearchList/index.tsx Outdated
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: 63f2565bfa

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

@dubielzyk-expensify
Copy link
Copy Markdown
Contributor

I think we spoke about having more spacing above the search fields when they appear? 20px?

CleanShot 2026-05-27 at 19 34 57@2x

Otherwise it's looking pretty good to me. Curious to do an adhoc too

@bernhardoj
Copy link
Copy Markdown
Contributor Author

Yeah, we did, it's the old recordings 😅

image

Let's spin an adhoc build

@github-actions
Copy link
Copy Markdown
Contributor

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

});
});

describe('getKeywordQueryWithCurrentSearchContext', () => {
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

This is removed from the revert PR, so added it back here.

@dubielzyk-expensify
Copy link
Copy Markdown
Contributor

Do we want auto-focus here @trjExpensify and @Expensify/design ?

CleanShot.2026-05-27.at.20.06.40.mp4

Also every other "search" field has Search as the label but category says category.

(I realize some of these things are perhaps outside of this PR or maybe mentioned before, but I'm just mentioning it 😅)

I think we also need to do something about this in a follow-up cause it's not obvious that there's a to date here:
CleanShot 2026-05-27 at 20 08 40@2x

Part of me also wanna auto-close the popover when applying a filter, but I worry a bit about how annoying it could for those who wanna apply many filters. I might lean to do it, but I don't feel strongly so curious what @Expensify/design thinks.

@bernhardoj amazing job on this btw. Always such high quality and attention to detail. Really appreciate it!

@bernhardoj
Copy link
Copy Markdown
Contributor Author

Do we want auto-focus here

The previous discussion was that we only auto-focus on the full-screen view. Fixed it.

@codecov
Copy link
Copy Markdown

codecov Bot commented May 27, 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 93.84% <ø> (ø)
src/SCREENS.ts 100.00% <ø> (ø)
...rc/components/Icon/chunks/expensify-icons.chunk.ts 0.00% <ø> (ø)
...s/AdvancedFilters/useFullscreenAdvancedFilters.tsx 100.00% <100.00%> (ø)
...mponents/Search/FilterDropdowns/DropdownButton.tsx 88.88% <100.00%> (ø)
.../Search/SearchPageHeader/DatePickerFilterPopup.tsx 0.00% <ø> (ø)
...h/SearchPageHeader/SearchDisplayDropdownButton.tsx 75.00% <100.00%> (-18.34%) ⬇️
...Search/SearchPageHeader/SearchFiltersBarNarrow.tsx 70.00% <100.00%> (+1.57%) ⬆️
...c/components/Search/hooks/useUpdateFilterQuery.tsx 40.00% <ø> (+9.23%) ⬆️
...ents/Table/TableFilterButtons/buildFilterItems.tsx 47.45% <ø> (ø)
... and 54 more
... and 92 files with indirect coverage changes

@shawnborton
Copy link
Copy Markdown
Contributor

I'm pretty torn on closing or not - I can see an argument that you might want to keep adding filters instead of just one, but it's really hard to know for sure. I would probably leave it open until the user clicks outside?

Agree where you both landed on auto-focus as well.

@aimane-chnaif
Copy link
Copy Markdown
Contributor

Are we still waiting on feedback or more to fix yet? Or ready for review?

@bernhardoj
Copy link
Copy Markdown
Contributor Author

Ready for review

Comment thread src/ROUTES.ts
SEARCH_ADVANCED_FILTERS_CONTENT: {
route: 'search/filters/:filterKey',
getRoute: (filterKey: SearchFilterKey | UserFriendlyKey) => `search/filters/${filterKey}` as const,
},
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.

For mobile view, any reason for not using existing legacy filter pages?

App/src/ROUTES.ts

Lines 747 to 756 in 52e1696

SEARCH_ADVANCED_FILTERS: {
route: 'search/filters/:filterKey?/:subPage?',
getRoute: (filterKey?: SearchFilterKey | UserFriendlyKey, subPage?: string) => {
const baseRoute = `search/filters/${filterKey ?? ''}` as const;
if (!subPage || !filterKey) {
return baseRoute;
}
return `${baseRoute}/${subPage}` as const;
},
},

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.

As we're going with navigation path, why not just reorder filter menu items in old filters page but completely refactored?

@JS00001 JS00001 self-requested a review May 27, 2026 17:01
@aimane-chnaif
Copy link
Copy Markdown
Contributor

aimane-chnaif commented May 27, 2026

Bug: janky animation when open amount filter

diff.mov

Copy link
Copy Markdown
Contributor

@luacmartins luacmartins left a comment

Choose a reason for hiding this comment

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

Let's make sure that all blockers are fixed #91684

@aimane-chnaif
Copy link
Copy Markdown
Contributor

Let's make sure that all blockers are fixed #91684

Regarding No receipt tooltip in Has filter, we're still discussing expected behavior in #91683 (comment)

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