You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reason the problem was not caught earlier is that the unawaited_futures lint only applies to async functions. To have the same effect in non-async functions, we can try enabling the discarded_futures in the code analysis and check if the problems reported by it are real problems or not (in other words, check if the lint rule is effective on our codebase).
The text was updated successfully, but these errors were encountered:
I have created an issue in the Dart issue tracker to see if this is an issue they are looking to fix in the Dart analyzer or not. If they are interested in having it fixed, I can look into contributing an update to the lint rules with a PR to the Dart SDK.
This does bring another question to mind: don't we have a "unawaited_futures" lint enabled? If yes, why wasn't this caught earlier?
Originally posted by @limwa in #1365 (comment)
The reason the problem was not caught earlier is that the unawaited_futures lint only applies to async functions. To have the same effect in non-async functions, we can try enabling the discarded_futures in the code analysis and check if the problems reported by it are real problems or not (in other words, check if the lint rule is effective on our codebase).
The text was updated successfully, but these errors were encountered: