-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
chore: add @typescript-eslint/require-await for notice error and remove unnecessary async #9011
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
Conversation
View your CI Pipeline Execution ↗ for commit cf3e774.
☁️ Nx Cloud last updated this comment at |
3ca7212
to
d6fb2d3
Compare
d6fb2d3
to
36542e9
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #9011 +/- ##
===========================================
+ Coverage 44.47% 58.86% +14.39%
===========================================
Files 203 138 -65
Lines 8104 5358 -2746
Branches 1804 1425 -379
===========================================
- Hits 3604 3154 -450
+ Misses 4066 1913 -2153
+ Partials 434 291 -143 🚀 New features to boost your workflow:
|
since we want this rule everywhere, please enable it in |
@TkDodo If you're referring to the whole query monorepo, would it be okay to proceed with a single PR that removes the unnecessary async keyword and adds the corresponding lint rule? I was thinking that combining them might help reduce the overhead from having to split and manage multiple PRs for related changes. |
@minseong0324 yes, you can add multiple PRs that will work towards that eslint rule, but please only one PR at the very end that enables the eslint rule in the root config. I don’t want this setting set to true in multiple eslint configs. The eslint configs in each package are only meant for really package specific overrides. For example, the react lint rules only make sense in react lated packages. But something that we want everywhere should be enabled in the root config. |
No description provided.