Repository navigation
enable unawaited_futures analysis option #5793
Description
Activity
- modified the milestone:
on Sep 12, 2016 This might be WONTFIX. We rarely await futures and it's not clear it would make the code cleaner. Most of our futures are harmless to ignore (e.g. the ones from animation controllers), and most can never throw errors so awaiting them to catch the error doesn't really help.
- modified the milestones: ,
on Feb 3, 2017 FYI, recent updates to
package:testhave made this even less likely to provide any value -- dart-lang/test#529 (comment)Closing this as WONTFIX makes sense to me.
- added a commit that references this issue
on Feb 15, 2017 - added a commit that references this issue
on Jul 19, 2018 - added a commit that references this issue
on Jul 19, 2018 This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.- locked as resolved and limited conversation to collaborators
on Aug 8, 2021
Enable the unawaited_futures analysis option in the 2 flutter repo analysis option files and cleanup the generated warnings.