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 (don't just cc him here, he won't see it! He's on Discord!).

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.

Please add all properties and this PR requires a test.

Please add all properties and this PR requires a test.

Fixed.

Please add all properties and this PR requires a test.

cc @TahaTesser Could you have a look at this again? It needs two flutter members to review.

@Piinks Could you do a secondary review?

@wangying3426
Can you rebase or add an empty commit so Google Testing passes to get this merged?

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

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

@wangying3426 Can you rebase or add an empty commit so Google Testing passes to get this merged?

There seem to be some problem for Google testing, it has failed several times.