-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Docs: differences between recommended and strict configs not mentioned on the website #8712
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
Comments
I can't reproduce this in the playground locally. https://typescript-eslint.io/play/#ts=5.4.2&fileType=.ts&code=IYZwngdgxgBAZgV2gFwJYHsIwO7oE4DWAFAJQwDeMAvgFA0Bu6qAJjvsSQNw1A&eslintrc=N4KABGBEBOCuA2BTAzpAXGUEKQAIBcBPABxQGNoBLY-AWhXkoDt8B6Jge1oDN4OBDfMwDmtYtA4BbSshTooiaBOiRwYAL4h1QA&tsconfig=&tokens=false The default config for the rule hasn't changed:
#8364 added the option for rules to have different defaults in |
I think this changed for strict rule set. In recommended it was not complaining with void. But when enabling strict rule set after update, I got bunch of errors. |
Got it - I'm realizing now I really should have done more to document this. Sorry for the confusion. I'll retarget this as a docs issue and send a PR very soon. |
@JoshuaKGoldberg i would probably say that this is one of those changes a lot of people would disagree with and want to reconfigure. Using The other config changes are tweaks to rules - but this one is a pretty big shift in the coding style. Perhaps we should revert this specific config change and save it for a major, given how disruptive it will be for users? |
Yeah, makes sense. I'll send that too. 👍 |
@JoshuaKGoldberg could you also add a note to release notes that some default settings may have changed between recommended and strict? I’m not sure how that would be worded but I think that is the first place people will look right now :) |
Good idea, thanks! Added to https://github.com/typescript-eslint/typescript-eslint/releases/tag/v7.3.0. |
https://github.com/typescript-eslint/typescript-eslint/releases/tag/v7.3.1 is released with the revert. |
Before You File a Bug Report Please Confirm You Have Done The Following...
Playground Link
The playground does currently not allow to specify 7.3.0
Repro Code
The rule
@typescript-eslint/no-floating-promises
no longer seems to have the optionignoreVoid
set to true by default in 7.3.0.When upgrading from 7.2.0 to 7.3.0 the following code report an error and only explicitly specifying
ignoreVoid: true
it works as in 7.2.0.ESLint Config
tsconfig
Expected Result
No errors when using void
Actual Result
Even when using void an error is reported
Additional Info
No response
The text was updated successfully, but these errors were encountered: