Handling the "unnecessary await" linter warning #1177
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The initial goal of this PR was to remove some await because of this:

https://codeclimate.com/github/kleros/kleros-v2/web/src/hooks/queries/useCounter.ts?from_sha=d01a8886&to_sha=c04e8c78
Looking further into, ESLint has deprecated the
no-return-await
rule:It turns out that there is a tradeoff between a potentially small perf improvement (without
await
, but it encourages bad dev habits) vs better stack traces in the V8 engine only (withawait
).This additional rule
@typescript-eslint/return-await
provides more granularity