☁️ Nx Cloud Report

CI ran the following commands for commit42701f5. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

Sent with 💌 fromNxCloud.

Thanks for the PR,@uhyo!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!

🙏Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently onhttps://opencollective.com/typescript-eslint. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitorsper day.

❌ Deploy Preview fortypescript-eslint failed.

🔨 Explore the source changes:42701f5

🔍 Inspect the deploy log:https://app.netlify.com/sites/typescript-eslint/deploys/6217b76f95b0d100079e1af4

Codecov Report

Merging#4541 (42701f5) intomain (823b945) willincrease coverage by0.03%.
The diff coverage is98.11%.

@@            Coverage Diff             @@##             main    #4541      +/-   ##==========================================+ Coverage   94.62%   94.65%   +0.03%==========================================  Files         149      150       +1       Lines        8072     8162      +90       Branches     2581     2617      +36     ==========================================+ Hits         7638     7726      +88- Misses        239      241       +2  Partials      195      195

Flags with carried forward coverage won't be shown.Click here to find out more.

...is there a collective group project or hackathon going on or something? A micro viral tweet? I did not expect this PR to be so popular so quick after posting 😄

🙏 ✨

@JoshuaKGoldberg Thank you for review!
Coverage is now 100% and I addressed your points. 🙏

thanks for the improvement@uhyo ! I'm wondering, is there a way to disable only thePromise-returning function provided to attribute where a void return was expected error? I find it too strict for my React codebase. I have code like this in many places:

functionMyButton(){constonClick=async()=>{constb=awaitdoSomething();doSomethingElse(b);}return<buttononClick={onClick}>Clickme!</button>;}

and now that error is being (correctly!) detected on those places.

I know I could do'@typescript-eslint/no-misused-promises': ['error', { checksVoidReturn: false }],, but I don't want to disable all the other error cases. I'm wondering if something more like'@typescript-eslint/no-misused-promises': ['error', { checksVoidReturningArgument: false }], exists / is on the roadmap.

As per our contributing guide - please don't comment on closed PRs.

Instead please use issues to start new discussions and find existing ones like#4619 or#4609