-
Notifications
You must be signed in to change notification settings - Fork 460
[eslint-factory] Align require-mkdirsync-try-catch with unbound fs resolution
#46902
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
pelikhan
merged 4 commits into
main
from
copilot/eslint-factory-require-mkdirsync-try-catch
Jul 21, 2026
+30
−3
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
e774985
Initial plan
Copilot db69df8
fix(eslint-factory): align mkdirsync try/catch rule with fs-sync reso…
Copilot 4bae4e1
fix(eslint-factory): only use allowUnboundFsIdentifier fallback when …
Copilot c875afc
Merge branch 'main' into copilot/eslint-factory-require-mkdirsync-try…
github-actions[bot] File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Silent regression coverage gap: the
mock-fsvalid case was removed instead of being moved toinvalid, leaving the false-positive completely untested.💡 What this hides
The deleted test case was:
`const fs = require("mock-fs"); fs.mkdirSync(dir, { recursive: true });`With
allowUnboundFsIdentifier: true,isIdentifierBoundToFsModuleis skipped for any identifier namedfs— including one explicitly bound tomock-fs. That means this call will now be incorrectly flagged as a violation.The correct fix is to either:
invalid(to document the now-intended behavior — report evenmock-fs-bound calls), orfs.As written, the test silently accepts the regression rather than documenting it.