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

🐛 Bug: Normalize ordering and printing of ESLint options and extensions #1715

Closed
3 tasks done
JoshuaKGoldberg opened this issue Dec 3, 2024 · 1 comment · Fixed by #1723
Closed
3 tasks done
Assignees
Labels
status: accepting prs Please, send a pull request to resolve this! type: bug Something isn't working :(

Comments

@JoshuaKGoldberg
Copy link
Owner

Bug Report Checklist

  • I have tried restarting my IDE and the issue persists.
  • I have pulled the latest main branch of the repository.
  • I have searched for related issues and found none that matched my issue.

Expected

eslint.config.js should be as straightforward as possible to automate. This is both to make #1670 easier and to remove unintuitive ad hoc preferences from its contents.

Actual

There are a few differences.

The biggest right now is the way plugin entries in the array are ordered. It's ... kind of alphabetical? They're somewhat in alphabetical order at first for direct property accesses and spreads thereof, and then objects in order of files - sort of?

Also, ignores isn't fully alphabetical, and linterOptions could be collapsed into one line.

Additional Info

Split out of #1670.

💖

Copy link

🎉 This is included in version v1.77.0 🎉

The release is available on:

Cheers! 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: accepting prs Please, send a pull request to resolve this! type: bug Something isn't working :(
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant