discarded_futures
Don't invoke asynchronous functions in non-async
blocks.
This rule is available as of Dart 2.18.
This rule has a quick fix available.
Details
#Making asynchronous calls in non-async
functions is usually the sign of a programming error. In general these functions should be marked async
and such futures should likely be awaited (as enforced by unawaited_futures
).
DON'T invoke asynchronous functions in non-async
blocks.
BAD:
void recreateDir(String path) {
deleteDir(path);
createDir(path);
}
Future<void> deleteDir(String path) async {}
Future<void> createDir(String path) async {}
GOOD:
Future<void> recreateDir(String path) async {
await deleteDir(path);
await createDir(path);
}
Future<void> deleteDir(String path) async {}
Future<void> createDir(String path) async {}
Usage
#To enable the discarded_futures
rule, add discarded_futures
under linter > rules in your analysis_options.yaml
file:
linter:
rules:
- discarded_futures
Unless stated otherwise, the documentation on this site reflects Dart 3.5.3. Page last updated on 2024-07-03. View source or report an issue.