Maintain user defined order in search query

[ShridharGoel]

Explanation of Change

Maintain user defined order in search query. Now, inputs will not jump around and will remain at the same place where the user would have typed them.

Fixed Issues

$ #69394
PROPOSAL: #69394 (comment)

Tests

1. Go to Reports page.
2. Manual enter a query like type:expense-report date:this-month status:draft.
3. Press enter.
4. The entered term should remain at the place where it was written and should not get reordered.
5. Use form filter to change status to Approved and apply filter
6. The order of entered term could be changed.

• Verify that no errors appear in the JS console

Offline 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

Screen.Recording.2025-09-25.at.1.18.31.AM.mov

Android: mWeb Chrome

Screen.Recording.2025-09-25.at.1.16.58.AM.mov

iOS: Native

Simulator.Screen.Recording.-.iPhone.16.Plus.-.2025-09-25.at.01.01.14.mp4

iOS: mWeb Safari

Simulator.Screen.Recording.-.iPhone.16.Plus.-.2025-09-25.at.01.11.51.mp4

MacOS: Chrome / Safari

Screen.Recording.2025-09-25.at.1.12.56.AM.mov

MacOS: Desktop

Screen.Recording.2025-09-25.at.1.09.09.AM.mov

[melvin-bot]

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

[codecov]

Codecov Report

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

Files with missing lines	Coverage Δ
src/ROUTES.ts	12.62% <100.00%> (+0.09%)	⬆️
src/pages/Search/SearchPage.tsx	26.21% <100.00%> (ø)
...nents/Search/SearchPageHeader/SearchFiltersBar.tsx	71.13% <0.00%> (ø)
.../Search/SearchPageHeader/SearchPageHeaderInput.tsx	36.87% <0.00%> (ø)
...rc/components/Search/SearchRouter/SearchRouter.tsx	0.40% <0.00%> (ø)
src/components/Search/index.tsx	34.43% <0.00%> (ø)
src/libs/SearchParser/searchParser.js	82.73% <86.66%> (+0.09%)	⬆️
src/components/Navigation/SearchSidebar.tsx	0.00% <0.00%> (ø)
src/libs/SearchQueryUtils.ts	70.44% <61.87%> (+4.48%)	⬆️
... and 7 files with indirect coverage changes

[ShridharGoel]

@shubham1206agra This is ready for review.

[ShridharGoel]

@shubham1206agra Gentle bump on the review here.

[shubham1206agra]

@ShridharGoel Can you add some comments to the functions? The PR is quite complex and it might be hard to follow for everyone later too.

[ShridharGoel]

@shubham1206agra Some more comments have been added.

[shubham1206agra]

@ShridharGoel Can you add comments in src/libs/SearchQueryUtils.ts?

[ShridharGoel]

@shubham1206agra Added.

[ShridharGoel]

@shubham1206agra Do let me know if some part is unclear and needs more documentation.

[ShridharGoel]

@shubham1206agra @JS00001 How can we progress on the review for this? It's open since almost 2 weeks.

[JS00001]

Is this just waiting on review? If so, @shubham1206agra can you please re-review

[shubham1206agra]

@ShridharGoel Sorry, I was on leave last week. I will catch up to this PR.

[ShridharGoel]

Thanks!

[shubham1206agra]

Screen.Recording.2025-10-10.at.7.21.12.PM.mov

@ShridharGoel NAB: When selecting filter, the order is switching up. Can we maintain the order here somehow?

[shubham1206agra]

Screen.Recording.2025-10-10.at.7.25.38.PM.mov

@ShridharGoel If I use duplicate key, it does not remove the duplicate key. (Note - We should keep the first position of the key)

[JS00001]

Theres also conflicts

[ShridharGoel]

@shubham1206agra Can you check for duplicate entries now?

[shubham1206agra]

@ShridharGoel Can you fix the errors?

[ShridharGoel]

@shubham1206agra Updated.

[ShridharGoel]

@shubham1206agra Did you get a chance to check this? Thanks

[ShridharGoel]

@shubham1206agra Any update on this?

[JS00001]

Pinged in slack: https://expensify.slack.com/archives/C02NK2DQWUX/p1760702972360109

[eh2077]

@ShridharGoel I think we should update test steps to mention that the order of query could be changed when using form filter, see #71075 (comment). Wdyt?

[ShridharGoel]

@eh2077 I had already updated the test steps based on #71075 (comment), thanks for the suggestion

[eh2077]

LGTM 🚀

[ShridharGoel]

@JS00001 Can you have a look?

[eh2077]

@ShridharGoel Please take a look at conflicts, thanks!

[JS00001]

Please fix conflicts

[ShridharGoel]

@JS00001 Done

[eh2077]

Suggested change

[JS00001]

Great work on this, thank you!

[JS00001]

@ShridharGoel Can you please pull main to fix typechecks/jest?

[OSBotify]

✋ 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]

🚀 Deployed to staging by https://github.com/JS00001 in version: 9.2.67-0 🚀

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

[OSBotify]

🚀 Deployed to staging by https://github.com/JS00001 in version: 9.2.70-0 🚀

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

[OSBotify]

🚀 Deployed to production by https://github.com/mountiny in version: 9.2.70-0 🚀

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

[thesahindia]

This PR caused #87285. Explanation here.

[sobitneupane]

This PR caused #79952. When searching in #chat, the user was unintentionally being directed to type:expense in:#chat instead of type:chat in:#chat.