-
-
Notifications
You must be signed in to change notification settings - Fork 81
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
fix: normalized eslint.config.js ordering and trimming #1723
Conversation
{ | ||
extends: [vitest.configs.recommended], | ||
files: ["**/*.test.*"], | ||
rules: { | ||
// These on-by-default rules aren't useful in test files. |
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.
Removed intentionally. I don't think it was worth the space. This block is clearly for test files, and this list isn't something any project of mine has reasonably added to IIRC.
"@typescript-eslint/no-unsafe-assignment": "off", | ||
"@typescript-eslint/no-unsafe-call": "off", |
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.
🎉 Very happy that this has since been made unnecessary. I haven't looked deeply, but I'm betting some improvement to Vitest types changed an any
to something more precise.
For no-unsafe-assignment
, it's down to two any
types in Vitest. Filed: vitest-dev/vitest#7015
🎉 This is included in version v1.77.0 🎉 The release is available on: Cheers! 📦🚀 |
PR Checklist
status: accepting prs
Overview
Applies the standard ordering prototyped in #1670. That is, the flat config array elements are in the following order:
ignores
(now sorted), thenlinterOptions
...
s are no longer necessary as of feat(typescript-eslint): allow infinitely deep array nesting in config function and extends typescript-eslint/typescript-eslint#10333files
💖