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: upgrade ESLint to use new flat config #420

Merged
merged 1 commit into from
Jul 2, 2024

Conversation

Venefilyn
Copy link
Collaborator

@Venefilyn Venefilyn commented Jun 10, 2024

With ESLint 9 being out and plugins slowly migrating, this takes care of
the migration of ESLint config from package.json to its own
eslint.config.mjs. This is needed as package.json and .eslintrc is
deprecated

TODO:

  • Write new tests or update the old ones to cover new functionality.
  • Update doc-strings where appropriate.
  • Update or write new documentation in packit/packit.dev.
  • ‹fill in›

Fixes

Related to

Merge before/after

RELEASE NOTES BEGIN
Upgrade ESLint config structure
RELEASE NOTES END

@usercont-release-bot
Copy link

usercont-release-bot commented Jun 10, 2024

Preview: https://packit-dashboard-pr-420.surge.sh (deployed at Wed 26 Jun 2024, 15:09 UTC)

Copy link
Contributor

With ESLint 9 being out and plugins slowly migrating, this takes care of
the migration of ESLint config from package.json to its own
eslint.config.mjs. This is needed as package.json and .eslintrc is
deprecated
Copy link
Contributor

Copy link
Member

@lbarcziova lbarcziova left a comment

Choose a reason for hiding this comment

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

lgtm, thanks!

@Venefilyn Venefilyn added this pull request to the merge queue Jul 2, 2024
Merged via the queue into packit:main with commit 0b8052d Jul 2, 2024
4 checks passed
@Venefilyn Venefilyn deleted the chore/eslint-upgrade branch July 2, 2024 11:02
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