-
Notifications
You must be signed in to change notification settings - Fork 15
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
v3.0.0 #68
v3.0.0 #68
Conversation
Should the lower bound of the SDK stay at 3.0.0 instead of 3.1.0 for maximum compatibility? |
@GZGavinZhao |
Oh yes, you're right. Well, that's sad, we have to keep the min SDK bound at 3.1.0 then. |
Dart 3.2 is already released. |
I think we should keep min SDK bound to 3.1 unless there are packages/language features that prevents us from doing so.
I managed to migrate all of them. Browser tests (
|
Signed-off-by: Gavin Zhao <[email protected]>
Some tests show that mock-like behavior is not supported in null-safety mode: group('should be mock-like', () {
mockLikeTests(nullSafe: false);
});
group('should never be mock-like when opted-in to null-safety', () {
mockLikeTests(nullSafe: true);
}); Maybe remove all mock-like tests? I try to disable the null-safety option in the compile context. |
Found this: /// Whether this output has mock-like behavior.
///
/// The heuristic used to determine mock-like behavior is if the analyzed
/// class or one of its ancestors, other than [Object], implements
/// [noSuchMethod].
///
/// Note that is the value is _never_ true for null-safe libraries, as we no
/// longer support null streams/stream subscriptions in the generated code. |
I think this is ready for merge? |
@GZGavinZhao yes. |
No description provided.