Skip to content
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

Merged
merged 17 commits into from
Nov 29, 2023
Merged

v3.0.0 #68

merged 17 commits into from
Nov 29, 2023

Conversation

ykmnkmi
Copy link

@ykmnkmi ykmnkmi commented Nov 18, 2023

No description provided.

@GZGavinZhao GZGavinZhao self-requested a review November 18, 2023 17:49
@GZGavinZhao
Copy link

Should the lower bound of the SDK stay at 3.0.0 instead of 3.1.0 for maximum compatibility?

@ykmnkmi
Copy link
Author

ykmnkmi commented Nov 19, 2023

@GZGavinZhao mockito 5.4.3 which requires Dart SDK version ^3.1.0.

@GZGavinZhao
Copy link

Oh yes, you're right. Well, that's sad, we have to keep the min SDK bound at 3.1.0 then.

@ykmnkmi
Copy link
Author

ykmnkmi commented Nov 20, 2023

Dart 3.2 is already released. _tests/test is not updated. I also noticed old doc. comments to update.

@GZGavinZhao
Copy link

GZGavinZhao commented Nov 22, 2023

I think we should keep min SDK bound to 3.1 unless there are packages/language features that prevents us from doing so.

Regarding _tests/test, locally I was able to migrate all files to Dart 3 except 3:

  • _tests/test/core/linker/security_integration_test.dart
  • _tests/test/compiler/output/dart_emitter_test.dart
  • _tests/test/compiler/ast_directive_normalizer_test.dart

I managed to migrate all of them. Browser tests (-P browser) there were 2 failures (+787 ~11 -2), but I think those are trivial fixes. The real problem is with the vm tests (-P vm) (+159 ~4 -59). A majority of them are type 'Null' is not a subtype of X errors.

I'm not sure how I should merge the changes with yours. Do you want me to push to your existing working branch directly? I pushed the existing work on top of yours into the dart3 branch here. Feel free to work on top of those changes.

@ykmnkmi
Copy link
Author

ykmnkmi commented Nov 22, 2023

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.

@ykmnkmi
Copy link
Author

ykmnkmi commented Nov 22, 2023

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.

@GZGavinZhao GZGavinZhao mentioned this pull request Nov 23, 2023
17 tasks
@GZGavinZhao
Copy link

I think this is ready for merge?

@ykmnkmi ykmnkmi marked this pull request as ready for review November 26, 2023 06:41
@ykmnkmi
Copy link
Author

ykmnkmi commented Nov 26, 2023

@GZGavinZhao yes.

@GZGavinZhao GZGavinZhao merged commit 3149fa1 into angulardart-community:master Nov 29, 2023
26 checks passed
@ykmnkmi ykmnkmi deleted the 3.0.0 branch February 29, 2024 17:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants