Show view attr value in the query syntax - #81318
Conversation
|
@ShridharGoel 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] |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 36090f4c27
ℹ️ 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".
| if (view) { | ||
| title += ` view:${getUserFriendlyValue(view)}`; | ||
| } |
There was a problem hiding this comment.
Skip default view to avoid showing
view:table everywhere
Because parseSearchQuery always populates a default view (view: "table" in src/libs/SearchParser/searchParser.js), this new unconditional append will add view:table to user-visible query text and saved search names even when the user never specified a view. That changes the default search syntax UI and diverges from buildSearchQueryString which explicitly omits view unless it was set by the user. Consider checking whether the view was explicitly set or differs from the default before appending it.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
this is fine, because it adds view:table by default only when there is a group-by
Reviewer Checklist
Screenshots/VideosAndroid: HybridAppAndroid: mWeb ChromeiOS: HybridAppiOS: mWeb SafariMacOS: Chrome / SafariScreen.Recording.2026-02-04.at.12.52.50.AM.mov |
|
@srikarparsi 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] |
|
👋 looks like you have a conflict here now @cristipaval. @neil-marcellini @puneetlath @lakchote do one of you want to take over the internal review from Srikar? |
|
Hey @cristipaval, sorry I confused this with another PR that was still being worked on. I approved it and can re-approve it once conflicts are resolved |
Codecov Report✅ Changes either increased or maintained existing code coverage, great job!
|
|
🚧 @cristipaval has triggered a test Expensify/App build. You can view the workflow run here. |
|
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
|
🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
|
|
🚀 Deployed to staging by https://github.com/cristipaval in version: 9.3.16-0 🚀
|
|
🚀 Deployed to production by https://github.com/lakchote in version: 9.3.16-9 🚀
|
Explanation of Change
Fixed Issues
$ #81095
PROPOSAL:
Tests
type:expense group-by:category date:this-month view:barFiltersand thenSave search)Offline tests
N/A
QA Steps
Same as tests.
PR Author Checklist
### Fixed Issuessection aboveTestssectionOffline stepssectionQA stepssectioncanBeMissingparam foruseOnyxtoggleReportand notonIconClick)src/languages/*files and using the translation methodSTYLE.md) were followedAvatar, I verified the components usingAvatarare working as expected)StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))npm run compress-svg)Avataris modified, I verified thatAvataris working as expected in all cases)Designlabel and/or tagged@Expensify/designso the design team can review the changes.ScrollViewcomponent to make it scrollable when more elements are added to the page.mainbranch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTeststeps.Screenshots/Videos
Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
Screen.Recording.2026-02-03.at.17.42.57.mov