Skip to content

[No QA] Prune stale eslint-seatbelt entries for deleted files on merge to main - #98665

Merged
blimpich merged 9 commits into
mainfrom
chore/prune-stale-eslint-seatbelt-entries
Aug 14, 2026
Merged

[No QA] Prune stale eslint-seatbelt entries for deleted files on merge to main#98665
blimpich merged 9 commits into
mainfrom
chore/prune-stale-eslint-seatbelt-entries

Conversation

@roryabraham

@roryabraham roryabraham commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

eslint-seatbelt doesn't prune entries for deleted files. This is a known, unfixed upstream bug: justjake/eslint-seatbelt#15.)

This PR fixes that by:

  • Re-writing scripts/lint.sh in bun
  • Updating that script to automatically pruning all eslint-seatbelt entries for files that no longer exist.

Fixed Issues

$ #98676

Tests

Covered by CI.

  • Verify that no errors appear in the JS console

Offline tests

n/a

QA Steps

n/a

  • 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 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

N/A — no UI changes.

eslint-seatbelt never revisits a file's baseline row once the file is
deleted or renamed, so stale rows accumulate forever (upstream bug:
justjake/eslint-seatbelt#15). Add a script that drops rows for files
that no longer exist and run it in the push-to-main lint job, so the
existing OSBotify baseline auto-commit picks up the pruning too.
…mal lint flow

Combines the standalone prune step from the previous commit into the lint
script itself, and runs the Onyx.connect() bypass check in-process (via
import) instead of shelling out to a second bun process. Also fixes a type
declaration gap in the eslint-seatbelt readOnly patch (needed so lint.ts's
own readOnly handling typechecks) and adds the new env vars lint.ts reads
to src/types/env.d.ts, following the repo's existing ProcessEnv convention.
@melvin-bot

melvin-bot Bot commented Aug 14, 2026

Copy link
Copy Markdown

npm has a package.json file and a package-lock.json file. It seems you updated one without the other, which is usually a sign of a mistake. If you are updating a package make sure that you update the version in package.json then run npm install

Bun's $ shell needs @types/bun, which conflicts with the app's own global
types if loaded into the root tsconfig project (same tradeoff already
made for tests/tooling/CIGitLogic.test.ts). Repurposes the pre-existing,
unused scripts/tsconfig.json (a leftover from the removed ts-node setup)
to isolate lint.ts into its own @types/bun project, and points ESLint's
type-aware parserOptions at it for that one file. Also drops the
NODE_OPTIONS/SEATBELT_* entries added to src/types/env.d.ts in the
previous commit, since lint.ts's new isolated project doesn't inherit
that file and no longer needs them.
…ectory

Investigated widening the Bun-types carve-out from lint.ts to all of
scripts/, but generateTranslations.ts and eslint-report.ts import from
@src/*, which transitively pulls in enough of the app that it needs
ambient declarations this project's narrower `types` doesn't have
(asset modules, Onyx's generic augmentations) -- real typecheck
regressions, not just noise. Documents the tradeoff and the per-file
opt-in path instead.
lint.ts already runs under its isolated @types/bun project, so it can
lean on Bun's own APIs for the two things it used node:fs/node:path
for: existence checks and locating the repo root relative to the
script's own file.
The exists() check for each baseline row was awaited one at a time in
a for loop; since each check is independent, run them all concurrently
instead and keep only the synchronous removeFile mutation in the loop.
@roryabraham roryabraham changed the title Prune stale eslint-seatbelt entries for deleted files on merge to main [No QA] Prune stale eslint-seatbelt entries for deleted files on merge to main Aug 14, 2026
@roryabraham
roryabraham requested a review from blimpich August 14, 2026 22:45
@roryabraham
roryabraham marked this pull request as ready for review August 14, 2026 22:46
@roryabraham
roryabraham requested a review from a team as a code owner August 14, 2026 22:46
@melvin-bot
melvin-bot Bot requested review from cretadn22 and removed request for a team August 14, 2026 22:46
@melvin-bot

melvin-bot Bot commented Aug 14, 2026

Copy link
Copy Markdown

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

@roryabraham
roryabraham removed the request for review from cretadn22 August 14, 2026 22:46

@blimpich blimpich 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

@blimpich
blimpich merged commit 8b0c94c into main Aug 14, 2026
55 of 56 checks passed
@blimpich
blimpich deleted the chore/prune-stale-eslint-seatbelt-entries branch August 14, 2026 23:34
@github-actions

Copy link
Copy Markdown
Contributor

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

@OSBotify

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.

3 participants