Skip to content
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

chore: extract noPackagePrivateImports rule #4651

Merged
merged 1 commit into from
Nov 28, 2024

Conversation

arendjr
Copy link
Contributor

@arendjr arendjr commented Nov 27, 2024

Summary

Previously I moved the useImportRestrictions rule into noRestrictedImports, because they were too similarly named. But someone rightly pointed out they should've remained separate rules, so I've extracted the rule again and renamed it.

Test Plan

CI should remain green.

@arendjr arendjr requested review from a team November 27, 2024 19:45
@github-actions github-actions bot added A-Project Area: project A-Linter Area: linter L-JavaScript Language: JavaScript and super languages A-Diagnostic Area: diagnostocis labels Nov 27, 2024
Copy link

codspeed-hq bot commented Nov 27, 2024

CodSpeed Performance Report

Merging #4651 will not alter performance

Comparing arendjr:no-package-private-imports (b6cff4b) with next (aa9582f)

Summary

✅ 97 untouched benchmarks

Copy link
Member

@ematipico ematipico left a comment

Choose a reason for hiding this comment

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

I'll merge this right away, and I will fix the rest of the failures soon. Thank you @arendjr


# The rule `useImportRestrictions` has been renamed to `noPackagePrivateImports`

To avoid confusion with `noRestrictedImports`, `useImportRestrictions` has been
Copy link
Member

Choose a reason for hiding this comment

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

Since noRestrictedImports is a nursery rule, we can make this a patch, because nursery rules don't follow semver

@ematipico ematipico merged commit d8f91ba into biomejs:next Nov 28, 2024
8 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Diagnostic Area: diagnostocis A-Linter Area: linter A-Project Area: project L-JavaScript Language: JavaScript and super languages
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants