Skip to content

remove remaining inline selectors#72546

Merged
mountiny merged 28 commits intoExpensify:mainfrom
callstack-internal:remove-remaining-inline-selectors
Nov 5, 2025
Merged

remove remaining inline selectors#72546
mountiny merged 28 commits intoExpensify:mainfrom
callstack-internal:remove-remaining-inline-selectors

Conversation

@TMisiukiewicz
Copy link
Contributor

@TMisiukiewicz TMisiukiewicz commented Oct 14, 2025

Explanation of Change

Migrating the remaining inline selectors to stable selectors. They were most likely accidentally missed during migration or created while the migration was ongoing.

Fixed Issues

$ #70272
PROPOSAL:

Tests

  1. Open app
  2. Verify the app loads properly
  • Verify that no errors appear in the JS console

Offline tests

n/a

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
android.mov
Android: mWeb Chrome
iOS: Native
ios.mov
iOS: mWeb Safari
ios.web.mov
MacOS: Chrome / Safari
web.mov
MacOS: Desktop
desktop.mov

@TMisiukiewicz TMisiukiewicz requested a review from a team as a code owner October 14, 2025 08:46
@melvin-bot melvin-bot bot requested review from dukenv0307 and removed request for a team October 14, 2025 08:46
@melvin-bot
Copy link

melvin-bot bot commented Oct 14, 2025

@dukenv0307 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
Copy link

codecov bot commented Oct 14, 2025

Codecov Report

❌ Patch coverage is 41.26984% with 37 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
src/selectors/Policy.ts 12.50% 7 Missing ⚠️
src/pages/NewReportWorkspaceSelectionPage.tsx 0.00% 5 Missing ⚠️
src/pages/TransactionMerge/DetailsReviewPage.tsx 0.00% 4 Missing ⚠️
src/pages/ReportChangeWorkspacePage.tsx 0.00% 3 Missing ⚠️
src/selectors/ReportNameValuePairs.ts 62.50% 3 Missing ⚠️
...e/SearchFiltersReportFieldPage/ReportFieldList.tsx 0.00% 2 Missing ⚠️
...chAdvancedFiltersPage/SearchFiltersTaxRatePage.tsx 0.00% 2 Missing ⚠️
...pages/home/report/ReportActionItemParentAction.tsx 0.00% 2 Missing ⚠️
src/selectors/Onboarding.ts 0.00% 2 Missing ⚠️
...c/components/Navigation/NavigationTabBar/index.tsx 80.00% 1 Missing ⚠️
... and 6 more
Files with missing lines Coverage Δ
src/components/MigratedUserWelcomeModal.tsx 9.09% <ø> (ø)
src/components/ProductTrainingContext/index.tsx 91.66% <ø> (+28.33%) ⬆️
...components/SelectionList/ListItem/UserListItem.tsx 4.54% <100.00%> (+2.21%) ⬆️
src/components/TestDrive/TestDriveDemo.tsx 7.69% <ø> (+1.02%) ⬆️
src/hooks/useArchivedReportsIdSet.ts 100.00% <ø> (+27.27%) ⬆️
src/hooks/useIsPaidPolicyAdmin.ts 100.00% <100.00%> (ø)
src/hooks/useOnboardingFlow.ts 82.35% <ø> (ø)
src/hooks/useTransactionViolationOfWorkspace.tsx 72.72% <100.00%> (+72.72%) ⬆️
src/libs/Navigation/NavigationRoot.tsx 79.38% <ø> (ø)
src/pages/Search/EmptySearchView.tsx 80.89% <ø> (+80.89%) ⬆️
... and 18 more

... and 342 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@dukenv0307
Copy link
Contributor

3 more places

const [allPolicies] = useOnyx(ONYXKEYS.COLLECTION.POLICY, {selector: (c) => mapOnyxCollectionItems(c, policySelector), canBeMissing: true});

const [policyChatForActivePolicy] = useOnyx(ONYXKEYS.COLLECTION.REPORT, {

selector: (report) => !!report,

}
});

const transactionViolationSelector = (violations: OnyxCollection<TransactionViolations>) => {
Copy link
Contributor

Choose a reason for hiding this comment

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

let's use useCallback

* `true` means the onboarding flow is loading
* `false` means the onboarding flow is not loading
*/
function isOnboardingLoadingSelector(onboarding: OnyxValue<typeof ONYXKEYS.NVP_ONBOARDING>): boolean | undefined {
Copy link
Contributor

Choose a reason for hiding this comment

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

why don't we move it to selectors folder?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good call, I missed the fact that it's not there

@TMisiukiewicz
Copy link
Contributor Author

Updated ✅

Copy link
Contributor

@roryabraham roryabraham left a comment

Choose a reason for hiding this comment

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

@TMisiukiewicz Can you please upgrade eslint-config-expensify to include the no-inline-useOnyx-selector rule we added in Expensify/eslint-config-expensify#160, now that the ESLint 9 upgrade is complete?

@github-actions
Copy link
Contributor

⚠️ This PR is possibly changing native code and/or updating libraries, it may cause problems with HybridApp. Please check if any patch updates are required in the HybridApp repo and run an AdHoc build to verify that HybridApp will not break. Ask Contributor Plus for help if you are not sure how to handle this. ⚠️

@TMisiukiewicz
Copy link
Contributor Author

@roryabraham amazing! Bumped version to 2.0.92

@TMisiukiewicz TMisiukiewicz force-pushed the remove-remaining-inline-selectors branch from 2e64e20 to 6133146 Compare October 17, 2025 07:01
@dukenv0307
Copy link
Contributor

@TMisiukiewicz Can you please fix the eslint check?

@TMisiukiewicz
Copy link
Contributor Author

Should be good now!

@TMisiukiewicz
Copy link
Contributor Author

Looks like tests are flaky

@dukenv0307
Copy link
Contributor

@TMisiukiewicz we got the conflict, can you please merge main?

@TMisiukiewicz
Copy link
Contributor Author

done

@TMisiukiewicz TMisiukiewicz requested a review from a team as a code owner November 4, 2025 06:47
@melvin-bot melvin-bot bot requested review from JmillsExpensify and removed request for a team November 4, 2025 06:47
Copy link
Contributor

@JmillsExpensify JmillsExpensify left a comment

Choose a reason for hiding this comment

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

No product pr review required

@carlosmiceli
Copy link
Contributor

@TMisiukiewicz lint errors this time 🙇

@gelocraft
Copy link
Contributor

gelocraft commented Nov 4, 2025

@TMisiukiewicz lint errors this time 🙇

@TMisiukiewicz lint error happens because the number of warnings exceeds the limit of 131.

you can fix this by increasing the maximum warnings threshold in package.json lint script.

@gelocraft
Copy link
Contributor

I hope this PR gets merged today 🥺

@TMisiukiewicz
Copy link
Contributor Author

Resolved conflicts again

@carlosmiceli
Copy link
Contributor

All yours @roryabraham

@TMisiukiewicz
Copy link
Contributor Author

Praying for a merge before conflict happens... 🤣

@mountiny mountiny merged commit 47fdef9 into Expensify:main Nov 5, 2025
33 checks passed
@OSBotify
Copy link
Contributor

OSBotify commented Nov 6, 2025

🚀 Deployed to staging by https://github.com/mountiny in version: 9.2.46-0 🚀

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

@OSBotify
Copy link
Contributor

OSBotify commented Nov 7, 2025

🚀 Deployed to production by https://github.com/luacmartins in version: 9.2.46-3 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 failure ❌

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.

8 participants