It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat.

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

Thanks! Yeah, I can add the import with the fix! :)

So, I added the import, just like we have in another fix, but it is for some reason resulting in ~1000 import statements after running the fix. 🙃

@bwilkerson is there something wrong here?

Output:
output.txt

This pull request executed golden file tests, but it has not been updated in a while (20+ days). Test results from Gold expire after as many days, so this pull request will need to be updated with a fresh commit in order to get results from Gold.

For more guidance, visit Writing a golden file test for package:flutter.

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

This pull request is not suitable for automatic merging in its current state.

• The status or check suite customer_testing-linux has failed. Please fix the issues identified (or deflake) before re-applying this label.

Not sure why flutter_svg would be broken by this. Checked it out locally with/without this change and the test failure persists, cc @dnfield

Looks like it may be related to an engine change - does it help if you merge up to head?

This is up to date as of 30 minutes ago, the failure has persisted for a few days now of merging master a couple of times.

Synced again..

Caught up with @dnfield offline, this failure does not appear to make sense with this change, I am going to open a fresh PR to see if it resolves itself.

New PR is #88365