Skip to content

Conversation

@blasten
Copy link

@blasten blasten commented Oct 26, 2020

Fixes #66395

@flutter-dashboard flutter-dashboard bot added f: cupertino flutter/packages/flutter/cupertino repository f: material design flutter/packages/flutter/material repository. c: contributor-productivity Team-specific productivity, code health, technical debt. labels Oct 26, 2020
@google-cla google-cla bot added the cla: yes label Oct 26, 2020
@blasten
Copy link
Author

blasten commented Oct 26, 2020

@jonahwilliams I'm looking at merging this PR, which requires passing the --enable-experiment=non-nullable flag to the tool. Any thoughts?

@jonahwilliams
Copy link
Contributor

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?

@jakemac53
Copy link
Contributor

We are actively working on unblocking the flag flip so yes I would probably just wait if that is possible.

@blasten
Copy link
Author

blasten commented Oct 26, 2020

or go through all of the integration tests and provide the flag manually

Do you mean the Flutter gallery ones only? @jonahwilliams

@blasten
Copy link
Author

blasten commented Oct 26, 2020

Alright. Sounds good.

@pcsosinski
Copy link

gallery performance is a gate for being beta ready, so ideally we have this data asap

@jonahwilliams
Copy link
Contributor

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.

@pcsosinski
Copy link

talked to @leafpetersen and @a-siva this morning, waiting for the flag flip PR to land is the plan.

@jonahwilliams
Copy link
Contributor

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.

@pcsosinski
Copy link

the flag flip has landed, what's left to get this in?

@jonahwilliams
Copy link
Contributor

Looks like this needs to be rebased

@pcsosinski
Copy link

@blasten are you able to rebase this PR?

@blasten
Copy link
Author

blasten commented Nov 2, 2020

@pcsosinski Done

@blasten blasten requested a review from jonahwilliams November 2, 2020 23:21
Copy link
Contributor

@jonahwilliams jonahwilliams left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@blasten
Copy link
Author

blasten commented Nov 2, 2020

@jonahwilliams
Copy link
Contributor

We'd need new versions of all the plugins published with updated constraints

@tvolkert
Copy link
Contributor

tvolkert commented Nov 4, 2020

Seems to be blocked on #69771 and #69770 - correct?

@blasten
Copy link
Author

blasten commented Nov 4, 2020

I see. In the meanwhile, I will update the Dart SDK constraint for the plugins.

@blasten blasten requested a review from jonahwilliams November 6, 2020 01:05
Copy link
Contributor

@jonahwilliams jonahwilliams left a 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:
Copy link
Contributor

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: () {},
Copy link
Contributor

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.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@jonahwilliams
Copy link
Contributor

Fix for the font loader failure is flutter/engine#22370

@blasten
Copy link
Author

blasten commented Nov 6, 2020

@jonahwilliams I sent flutter/engine#22373. Should it be void or String??

@blasten blasten merged commit 7ba775a into flutter:master Nov 7, 2020
@blasten blasten deleted the gallery_test_nnbd branch November 7, 2020 04:38
@blasten
Copy link
Author

blasten commented Nov 7, 2020

The BUILD file for the Gallery package needs to turn null safety on, then it should just work. fyi @renyou

@mit-mit
Copy link
Member

mit-mit commented Nov 9, 2020

This was reverted in #70023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

c: contributor-productivity Team-specific productivity, code health, technical debt. f: cupertino flutter/packages/flutter/cupertino repository f: material design flutter/packages/flutter/material repository.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Migrate Flutter Gallery test to NNBD

7 participants