Category field when creating an expense in the selfDM#72756
Conversation
|
@parasharrajat 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] |
| // eslint-disable-next-line rulesdir/no-default-id-values | ||
| setNameValuePair(ONYXKEYS.NVP_ACTIVE_POLICY_ID, selectedPolicyID, activePolicyID ?? ''); | ||
| Navigation.goBack(backTo); | ||
| Navigation.navigate(navigateTo); |
There was a problem hiding this comment.
Why are we using navigate ?
There was a problem hiding this comment.
For example, in a case where user doesn't have a default workspace we cannot navigate him back to category page as he wasn't there yet.
It looks something like this CreateExpense -> SetDefaultWorkpsace -> CreateExpense/Category
There was a problem hiding this comment.
Where if we were to use a goBack it would navigate user back to CreateExpense
CreateExpense -> SetDefaultWorkpsace -> (backTo) CreateExpense
|
|
||
| const selectPolicy = (selectedPolicyID?: string) => { | ||
| if (!selectedPolicyID) { | ||
| if (!selectedPolicyID || !navigateTo) { |
There was a problem hiding this comment.
We should log a Log.hmm in navigate is not passed as this is important here.
|
There are some issues reported from previous PR so we should handle those first. |
Screenshots🔲 iOS / native28.10.2025_00.01.01_REC.mp4🔲 iOS / Safari28.10.2025_13.38.02_REC.mp4🔲 MacOS / Chrome27.10.2025_20.47.08_REC.mp427.10.2025_23.36.26_REC.mp4🔲 Android / native27.10.2025_23.34.46_REC.mp427.10.2025_23.36.26_REC.mp4 |
|
Note: On the workspace creation confirmation page after user has upgraded on upgrade flow, pressing back button on header takes you back to the expense creation confirmation page while it used earlier take you to the categories list, same as I don't think it is an issue. Talking about this page. 
|
…84-category-field-for-iou
parasharrajat
left a comment
There was a problem hiding this comment.
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 Issuessection 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
Testssection - I verified the steps for Staging and/or Production testing are in the
QA stepssection - 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 verified the steps for local testing are in the
- 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 tests pass on all platforms & I tested again on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
- 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 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.
toggleReportand notonIconClick). - I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g.
myBool && <MyComponent />. - 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 approved by marketing by adding the
Waiting for Copylabel for a copy review on the original GH to get the correct copy. - 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
- 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.
- 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 usingAvatarhave 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.js 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
thisproperly so there are no scoping issues (i.e. foronClick={this.submit}the methodthis.submitshould be bound tothisin the constructor) - Any internal methods bound to
thisare necessary to be bound (i.e. avoidthis.submit = this.submit.bind(this);ifthis.submitis never passed to a component event handler likeonClick) - 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
- 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 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
Avataris modified, I verified thatAvataris 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 form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added
Designlabel so the design team can review the changes.
- If a new page is added, I verified it's using the
ScrollViewcomponent to make it scrollable when more elements are added to the page. - If the
mainbranch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTeststeps. - I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.
🎀 👀 🎀 C+ reviewed
| }, []); | ||
|
|
||
| useEffect(() => { | ||
| if (isCreatingTrackExpense && realPolicyID !== undefined && policy?.pendingAction !== CONST.RED_BRICK_ROAD_PENDING_ACTION.ADD) { |
There was a problem hiding this comment.
@parasharrajat There was a previously deleted comment here about using realPolicyID.
I think you're right and it's a bit confusing. I haven't noticed that below we have similar condition when creating policyID for tracked and other expenses.
In both cases when isCreatingTrackExpense is true we return policyForMovingExpensesID. So I think we should actually pass this IMO instead of realPolicyID wdyt?
There was a problem hiding this comment.
Yes, it is better to simplify it.
|
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
|
🚀 Deployed to staging by https://github.com/cristipaval in version: 9.2.40-0 🚀
|
|
🚀 Deployed to staging by https://github.com/cristipaval in version: 9.2.40-0 🚀
|
|
@koko57 @parasharrajat this PR caused several blockers including #73704 |
|
@MonilBhavsar Not yet. I am reviewing these bugs. Most of these are no blockers. As this is a new feature, we are working on it here. Some edge cases are expected. Some of these reported issues are behaviours we can/should add, not issues. |
|
Thanks for tagging us, @MonilBhavsar. This is a new feature that has been reverted a few times already. This time, the issues are minor and occur in very rare cases (refer to the preconditions in the reproducible steps). |
|
🚀 Deployed to production by https://github.com/lakchote in version: 9.2.40-1 🚀
|
Explanation of Change
Fixed Issues
$ #71784
PROPOSAL:
Tests
Prerequisites: selfDM
User with no collect/control workspace at all
User with a collect/control workspace set as the default or a member of only one non-default workspace
User with several group workspaces, none of them set as default
Offline tests
QA Steps
// TODO: These must be filled out, or the issue title must include "[No QA]."
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.2025-10-16.at.15.22.23.mp4
Screen.Recording.2025-10-16.at.14.51.09.mp4
Screen.Recording.2025-10-16.at.14.50.45.mp4
MacOS: Desktop