-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Remove tear-off mocking in refresh_test #15869
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
CC @xster |
|
CC @aam |
|
LG! |
|
Learning things. This PR breaks compatibility with Dart 1 mode. Working on a fix that works in both modes. |
|
Still LG. Thanks for figuring it out! |
|
Green Travis. Go for it! |
|
Someone with write access should totally merge this PR 😁 😁 😁 |
|
Didn't realize you can't submit it, @srawlins . |
|
AppVeyor completed, ready to be submitted as soon as flutter-build turns green. |
|
Can we submit this PR. |
|
Please go ahead
…On Fri, Mar 23, 2018, 5:38 PM Siva ***@***.***> wrote:
Can we submit this PR.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#15869 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAXQ0XtOoBcFCcFJG_h8lmJCeYmN-KTlks5thZWEgaJpZM4S5HgB>
.
|
* Remove tear-off mocking in refresh_test * Comments * Analyzer fix * Final final final final mushroom mushroom! * Fix for Dart 1 AND Dart 2 semantics; anonymous closure over tear-off * Final final
Fixes #15849.
In Dart 2 semantics (so far...) Mock objects cannot have their methods torn off as a part of mocking.
Related to dart-lang/mockito#107.