-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Migrate Flutter gallery test to null safety #69048
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
|
@jonahwilliams I'm looking at merging this PR, which requires passing the |
|
You'll need to either wait for the flag flip when --enable-experiment is no longer necessary, or go through all of the integration tests and provide the flag manually. My understanding is that the flag flip is happening fairly soon, and this change does not need to be landed before that point. @leafpetersen or @jakemac53 to confirm? |
|
We are actively working on unblocking the flag flip so yes I would probably just wait if that is possible. |
Do you mean the Flutter gallery ones only? @jonahwilliams |
|
Alright. Sounds good. |
|
gallery performance is a gate for being beta ready, so ideally we have this data asap |
|
There are probably a hundred or so places that need --enable-experiment=non-nullable. Unless the beta plan is to ship the very first commit after the flag flip, waiting seems like a safe option to me. |
|
talked to @leafpetersen and @a-siva this morning, waiting for the flag flip PR to land is the plan. |
|
The test scripts themselves should not be migrated to null safety, otherwise you will get sound mode warnings about the test script dependencies. This is unimportant as we care about the app under test running in sound mode. |
|
the flag flip has landed, what's left to get this in? |
|
Looks like this needs to be rebased |
|
@blasten are you able to rebase this PR? |
|
@pcsosinski Done |
jonahwilliams
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You need to update the SDK constraint here:
I think it needs to be at least 2.12 to opt into null safety
abd77b6 to
dd9bdd4
Compare
|
We'd need new versions of all the plugins published with updated constraints |
|
I see. In the meanwhile, I will update the Dart SDK constraint for the plugins. |
jonahwilliams
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overal changes LGTM
There is one more failure in the customer testing shard due to a constraint on intl ^0.16 which does not grab the 0.17 version since the overall version is < 1.0.
| analyzer: | ||
| exclude: | ||
| - build/** | ||
| enable-experiment: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With the dart SDK constraint set to >=2.12.0-0 < 3 this shouldn't be necessary.
| icon: const Icon(Icons.add, size: 18.0), | ||
| label: const Text('DISABLED', semanticsLabel: 'DISABLED BUTTON 6'), | ||
| onPressed: null, | ||
| onPressed: () {}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be null so that the button stays disabled.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
|
Fix for the font loader failure is flutter/engine#22370 |
|
@jonahwilliams I sent flutter/engine#22373. Should it be |
|
The |
|
This was reverted in #70023 |
Fixes #66395