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.

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

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

@jeanluc243 If you'd like to continue with this PR, please sign the CLA, and see our CONTRIBUTING.md. Thanks!

@googlebot I signed it!

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

@jeanluc243 the change seems reasonable, but it looks like git is a bit confused. I would recommend following the contributing guide in CONTRIBUTING.md, specifically setting up a separate flutter checkout for contributing and branching off of upstream/aster

@jeanluc243 unfortunately because of a change I made and landed upstream, CI won't pass for this PR. The easiest way to fix this would be to fetch the latest upstream master locally, create a new branch off of the tip of master, and then re-create your changes (as it's only a few lines that shouldn't be difficult). This change will also require tests. Feel free to ping me on your new PR if you need help writing tests.

@jeanluc243 Since the PR has to be recreated following @christopherfujino's, I'm going to close this one. Thanks!