Jacob Richman
Jacob Richman
Fyi @scheglov
LGTM on the cherry pick. I've filed a separate issue for the right long term solution.
I'm seeing some bogus uses of `as FutureOr` in g3 likely caused by this issue. @stereotype441 what is the minimum we can do to prevent the tool from generating these...
Followed up with @stereotype441 offline and we agree that just preventing the tool from generating the `as FutureOr` is the most realistic solution. This will cause a few analysis errors...
I'd added that API to Flutter for use cases similar to this but never had time to implement in DevTools. Some things to consider: 1. Should polish to handle widgets...
There are a bunch. We should at least have all the lints enabled in g3. We could start with that and then turn on all other lints without massive false...
Wow didn't realize this was possible! A bunch of the tooling is going to be confused as your app has two UI isolates. Most of our tooling is assuming the...
Fyi @rrousselGit.
There are two bugs: 1. This is a Flutter framework bug dealing with stack traces from eval expression. The likely fix is a change in package:flutter 2. Why did the...