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

feat: eslint-utils => @eslint-community/eslint-utils #474

Merged
merged 1 commit into from
Apr 30, 2024

Conversation

aladdin-add
Copy link
Contributor

eslint-plugin-eslint-comments => @eslint-community/eslint-plugin-eslint-comments

@voxpelli
Copy link
Member

Would be great to get a linting into these projects to ensure we make these migrations for all of the community modules :P

@aladdin-add aladdin-add requested a review from bmish April 30, 2024 09:22
@aladdin-add
Copy link
Contributor Author

That's why I don't want to rename - esp. a widely used package. :)

@voxpelli
Copy link
Member

@aladdin-add We could make a shared config that adds no-restricted-require / no-restricted-import for the old names and use that within all of our repositories

@aladdin-add
Copy link
Contributor Author

It can be done, but I'm not very sure if it's necessary. These migrations are all one-time, and once they're done, they're no longer needed. 😄

@voxpelli
Copy link
Member

Until a new module is transferred and we need to be reminded to do it all again ;P

@aladdin-add aladdin-add merged commit 6db5604 into main Apr 30, 2024
14 checks passed
@aladdin-add aladdin-add deleted the feat/eslint-community branch April 30, 2024 12:12
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.

None yet

3 participants