Jacob Richman

Punting from 0.1.6

Fyi @DaveShuckerow This would be a good first use case for widget tests taht interact with a real Flutter application.

P2

I suspect this would also massively reduce the cost for rendering screenshots for all cases but full page transitions. Likely the dirty region API is a big part of why...

Fyi @bkonyi as another option would be have a first class dart:developer API for this rather than just a convention Flutter, DevTools, and IDEs follow.

Fyi @DanTup

We could even add quick fixes to use https://api.flutter.dev/flutter/widgets/DisposableBuildContext-class.html for many cases where BuildContext is used unsafely.

They aren't the same in the context of being called from a closure within the State object's build method. `this.context` is the same as the parameter only if the `State`...

Here is a concrete example: ```dart Widget build(BuildContext context) { return Button(onClick() async { _loading = true; await loadData(); assert(identical(this.context, context)); // this assert would fire if the Element has...

Here is a concrete example where `context` is not leaked and only the State object leaks if loadData never completes. Replacing `this.context` with `context` would mitigate the leak. ```dart Widget...