-
Notifications
You must be signed in to change notification settings - Fork 218
Prepare for Dart 3 #1811
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
Comments
|
Another thing to consider here is if we should actually change our lower bound to |
cc @mit-mit what is the timeline here? How soon will this package break in dart 3 (or is it already broken?). |
The plan was to land changes removing the APIs starting Monday, Dec 12th, in Dart main. The will be breaking in google3, where there's a copy of the package, which would then fail analysis after a google3 roll of the SDK. |
Ok, so its a P0 then? |
Fixes #1811 I also pre-emptively bumped our dep on matcher, which I think should be fine, but please push back if you disagree. Moves all null safety related tests into a legacy_tests directory.
Yes, I believe so |
The source currently contains several references to APIs scheduled for removal in Dart 3 (details here):
CyclicInitializationError
NullThrownError
Can we move the min up to 3.0, and start working on a dev release version for this?
The text was updated successfully, but these errors were encountered: