Skip to content

Fix selected default tax rate ordering in category rules - #96462

Merged
robertjchen merged 12 commits into
Expensify:mainfrom
marufsharifi:fix/category-default-tax-rate-selected-order
Aug 5, 2026
Merged

Fix selected default tax rate ordering in category rules#96462
robertjchen merged 12 commits into
Expensify:mainfrom
marufsharifi:fix/category-default-tax-rate-selected-order

Conversation

@marufsharifi

@marufsharifi marufsharifi commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Fixes the Category rules Default tax rate picker so the initially selected tax rate is moved to the top of long tax-rate lists.

Fixed Issues

$ #69184
PROPOSAL: #69184 (comment)

Tests

Preconditions:

  • Enable Rules and Taxes in workspace
  1. Go to Workspace settings > Categories.
  2. Open a category.
  3. Open Default tax rate.
  4. Select a tax rate lower in the list.
  5. Go back/reopen the same category's Default tax rate picker.
  6. Verify the selected tax rate appears at the top.
  7. Select another tax rate.
  8. Reopen the picker.
  9. Verify the newly selected tax rate appears at the top.
  • Verify that no errors appear in the JS console

Offline tests

Same as tests

QA Steps

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
  • 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 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 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)
  • 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)
  • 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.
  • 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.2026-07-30.at.11.51.23.PM.mov
Android: mWeb Chrome
Screen_Recording_20260730_234846_Chrome.mp4
iOS: Native
Screen.Recording.2026-07-31.at.12.05.10.AM.mov
iOS: mWeb Safari
Screen.Recording.2026-07-31.at.12.07.39.AM.mov
MacOS: Chrome / Safari
Screen.Recording.2026-07-30.at.11.28.57.PM.mov

@codecov

codecov Bot commented Jul 20, 2026

Copy link
Copy Markdown

Codecov Report

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

Files with missing lines Coverage Δ
...e/categories/DynamicCategoryDefaultTaxRatePage.tsx 87.80% <100.00%> (+87.80%) ⬆️
... and 14 files with indirect coverage changes

@marufsharifi
marufsharifi marked this pull request as ready for review July 30, 2026 19:42
@marufsharifi
marufsharifi requested review from a team as code owners July 30, 2026 19:42
@melvin-bot
melvin-bot Bot requested review from linhvovan29546 and removed request for a team July 30, 2026 19:43
@melvin-bot

melvin-bot Bot commented Jul 30, 2026

Copy link
Copy Markdown

@linhvovan29546 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 requested review from flaviadefaria and removed request for a team July 30, 2026 19:43
@linhvovan29546

Copy link
Copy Markdown
Contributor

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

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: a188209923

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

const [draftTaxRate, setDraftTaxRate] = useState<string>();
const selectedTaxRate = draftTaxRate ?? persistedTaxRate;
const hasChanges = !!selectedTaxRate && selectedTaxRate !== persistedTaxRate;
const initialSelectedTaxRate = useInitialSelection(selectedTaxRate, {resetOnFocus: true});

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Refresh the initial tax snapshot after policy loads

When this screen is opened from a cold start/deep link and usePolicy() is still empty while AccessOrNotFoundWrapper shows its loading state, this snapshots selectedTaxRate as undefined. Since no isVisible/loaded condition is supplied to refresh the snapshot when the Onyx policy later arrives on the same focused screen, initialSelectedTaxRate can remain empty and moveInitialSelectionToTop becomes a no-op, leaving the persisted tax rate buried in long tax lists—the exact case this change is meant to fix. Gate the snapshot on the tax data being loaded or refresh it when persistedTaxRate becomes available.

Useful? React with 👍 / 👎.

@marufsharifi

Copy link
Copy Markdown
Contributor Author

@linhvovan29546 I've addressed the feedback, you can take another look when you get a chance, thanks

@@ -94,7 +103,7 @@ function DynamicCategoryDefaultTaxRatePage({
onBackButtonPress={() => Navigation.goBack(categorySettingsBackPath)}
/>
<SelectionList

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.

We should update initiallyFocusedItemKey={persistedTaxRate} to initiallyFocusedItemKey={initialSelectedTaxRate} instead.

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.

Since the pin already keeps the selected rate on top, I removed initiallyFocusedItemKey — with it, the list auto-scrolled to the tapped rate on every selection. Replaced it with shouldScrollToFocusedIndexOnMount={false}

@linhvovan29546 linhvovan29546 Aug 4, 2026

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.

That would introduce a regression. On the first arrow key press, the next/previous item is not focus. On the main branch, the next/previous item is focus

Screen.Recording.2026-08-04.at.17.27.08.mov

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.

Thanks, I just missed that. It has been fixed now

@linhvovan29546

linhvovan29546 commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Bug: The list scrolls when selecting an item. It shouldn't scroll.

Screen.Recording.2026-08-03.at.16.27.55.mov

@marufsharifi

Copy link
Copy Markdown
Contributor Author

Bug: The list scrolls when selecting an item. It shouldn't scroll.

@linhvovan29546 Thanks for catching that! This is fixed now.

@linhvovan29546

linhvovan29546 commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

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 Issues section 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 Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • 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 checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • 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 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 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)
  • 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 using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately
    • 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
    • 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 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 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.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this 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 have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
telegram-cloud-document-5-6312311029749522500.mp4
Android: mWeb Chrome
telegram-cloud-document-5-6312311029749522501.mp4
iOS: HybridApp
Screen.Recording.2026-08-05.at.14.57.58.mov
iOS: mWeb Safari
Screen.Recording.2026-08-05.at.14.36.57.mov
MacOS: Chrome / Safari
Screen.Recording.2026-08-05.at.14.34.31.mov

@linhvovan29546

Copy link
Copy Markdown
Contributor

@marufsharifi Could you please merge main again? Thanks

@linhvovan29546

Copy link
Copy Markdown
Contributor

Could you please fill in the QA Steps section as well? Thanks!

@linhvovan29546 linhvovan29546 left a comment

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.

@melvin-bot
melvin-bot Bot requested a review from robertjchen August 5, 2026 09:05

@robertjchen robertjchen left a comment

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.

LGTM!

@robertjchen
robertjchen merged commit 9cc573e into Expensify:main Aug 5, 2026
37 of 38 checks passed
@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

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

@OSBotify

OSBotify commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

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.

4 participants