[No QA] chore(eslint): enable unicorn/prefer-set-has lint rule

[gelocraft]

Explanation of Change

• bump eslint-config-expensify to 2.0.94
• temporarily disabled unicorn/prefer-set-has rule violations ( will be fixed in my follow-up PRs )

Fixed Issues

$ #67421
PROPOSAL: #67421 (comment)

Tests

• 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]."

• 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: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

[melvin-bot]

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

[github-actions]

⚠️ 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. ⚠️

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[gelocraft]

I have read the CLA Document and I hereby sign the CLA

[gelocraft]

don't merge yet

[gelocraft]

@roryabraham other rule violations coming from unicorn/prefer-set-has need to be fixed manually, so I’ve temporarily added inline eslint-disable comments to suppress those errors.

I'll open a follow-up PR to manually fix those non-autofixable files.

For now, I think it’s best to merge this PR since my fork quickly falls behind upstream (over 300 commits this morning), and I’ve had to repeatedly redo the autofixes, manually disable non-autofixable files to suppress errors temporarily, and resolve conflicts each time I sync my fork and rebase my pr branch to upstream/main.

[roryabraham]

don't merge yet

Pro-tip: if you open a PR as draft or prefix the title with [WIP] it will not be mergeable

[roryabraham]

I’ve temporarily added inline eslint-disable comments to suppress those errors ... I'll open a follow-up PR to manually fix those non-autofixable files ... For now, I think it’s best to merge this PR since my fork quickly falls behind upstream

Oh, apologies for missing this comment. That makes plenty of sense. Sounds great!

[gelocraft]

@roryabraham my fork tends to fall behind quickly, and each time I rebase my PR branch, more files require fixing. To manage this efficiently, I first ran autofixes for all autofixable files. For the remaining non-autofixable ones, I temporarily added inline disables and plan to address them in a follow-up PR.

[gelocraft]

@roryabraham don't merge yet, I'll rebase my pr branch again to upstream/main.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

Files with missing lines	Coverage Δ
src/components/Form/InputWrapper.tsx	100.00% <ø> (ø)
...nents/ReportActionItem/MoneyRequestReceiptView.tsx	2.04% <ø> (ø)
src/components/ScrollOffsetContextProvider.tsx	45.94% <ø> (ø)
src/components/Search/SearchAutocompleteList.tsx	0.60% <ø> (ø)
...nents/Search/SearchPageHeader/SearchFiltersBar.tsx	0.00% <ø> (ø)
src/components/TagPicker.tsx	0.00% <ø> (ø)
src/components/UploadFile.tsx	0.00% <ø> (ø)
src/hooks/useAdvancedSearchFilters.ts	0.00% <ø> (ø)
src/hooks/useDeleteTransactions.ts	19.11% <ø> (ø)
src/hooks/useSidebarOrderedReports.tsx	88.61% <ø> (ø)
... and 27 more

... and 2 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.

[roryabraham]

If you're having issues with conflicts you could always migrate a smaller subset of these without actually enabling the rule, then enable the rule after more are migrated. Up to you 🙂

[gelocraft]

@roryabraham @sobitneupane ready for merge

#72546 just got merged

[joekaufmanexpensify]

No product considerations here. Removing myself and unsubscribing

[gelocraft]

@roryabraham ready for merge

[roryabraham]

conflicts again

[gelocraft]

conflicts again

resolved

[gelocraft]

@roryabraham ready for merge

[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/roryabraham in version: 9.2.47-0 🚀

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

[mvtglobally]

@roryabraham Is there anything to QA in this PR?

[roryabraham]

nope!

[OSBotify]

🚀 Deployed to production by https://github.com/cristipaval in version: 9.2.47-1 🚀

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