Configs: Last round of "final" changes to configs for v6 #7130
Closed
JoshuaKGoldberg
announced in
Community Feedback
Replies: 2 comments 1 reply
-
Coming over from #7138:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Technically the |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Following #6014, I described the changes in #7110 as the "final v6 changes to configs". That was inaccurate - it was the final changes to configs before trying them out in real-world projects (#6760). Now that we've tried things out, there are a few more changes I think we should make...
Increasing strictness:
no-explicit-any
: It was moved fromrecommended
tostrict
, but I think we should move it back. Most projects shouldn't be usingany
.strict-boolean-expressions
: SwitchallowNullableEnum
tofalse
by default, per Changes to configurations for 6.0.0 #6014 (comment)Decreasing strictness:
no-confusing-void-expressions
: It was added tostylistic-type-checked
but I think it's too opinionated for many users, especially for those working in JSX-based frameworks. I think we should remove it fromstylistic-type-checked
for now.(this is inno-mixed-enums
: It was added torecommended
, but I think it's a rare enough edge case that a large percentage of consumers wouldn't care for the rule. I think we should instead move it tostrict
for now.strict-type-checked
, I was wrong)sort-type-constituents
: It was added tostylistic
. It's pretty nitpicky without actual bug-catching and I think many users would be by it. I think we should remove it fromstylistic
for now....anything else that's come up & we should adjust for?
Beta Was this translation helpful? Give feedback.
All reactions