3 ms·
I do not want to be mean but I think you'd be much better served with ESLint rules to yell at you when you don't await when you should or do when you shouldn't.
by joshstrange 1y ago
I do not want to be mean but I think you'd be much better served with ESLint rules to yell at you when you don't await when you should or do when you shouldn't.
This should _not_ be an automatic operation since it can change behavior in ways that will be unclear to the developer (completely undoing any gain from them being added automatically).
- theThree 1y agoYou can still control it by adding "//no-await". In fact, the "//no-await" makes me feel more clear.
- nextweek2 1y agoI created a ticket, using comments is not necessary because there is already the `void` syntax for when you don't want to wait: https://github.com/stanNthe5/typescript-autoawait/issues/1 https://github.com/stanNthe5/typescript-autoawait/issues/1
- nextweek2 1y agoIt should be noted that there is already a lint rule for this: https://typescript-eslint.io/rules/no-floating-promises/ https://typescript-eslint.io/rules/no-floating-promises/