Update FadeInImage to use new Image APIs#33370
Merged
tvolkert merged 2 commits intoflutter:masterfrom May 31, 2019
tvolkert:fade_in_image
Merged
Update FadeInImage to use new Image APIs#33370tvolkert merged 2 commits intoflutter:masterfrom tvolkert:fade_in_image
tvolkert merged 2 commits intoflutter:masterfrom
tvolkert:fade_in_image
Conversation
Hixie
reviewed
May 27, 2019
Hixie
reviewed
May 27, 2019
Hixie
reviewed
May 27, 2019
Hixie
reviewed
May 27, 2019
Hixie
reviewed
May 27, 2019
Hixie
reviewed
May 27, 2019
Hixie
reviewed
May 27, 2019
Hixie
reviewed
May 27, 2019
Hixie
reviewed
May 27, 2019
Contributor
Author
|
@Hixie I significantly re-worked this class. In the process, I got rid of two instance variables:
PTAL. |
goderbauer
reviewed
May 28, 2019
This updates FadeInImage to use the new Image.frameBuilder API (added in #33369), to greatly simplify the implementation of FadeInImage. This also removes the FadeInImage.placeholderSemanticLabel property. This property was added in #28799 for the sake of completeness (the bug it fixed was the lack of any semantic label support in FadeInImage), but a placeholder is a transient visual artifact, not something that affects the underlying semantic meaning of the image.
Contributor
Author
|
Ok, this has been rebased off of 6884146. I've updated the PR description to account for the breaking change. PTAL. |
goderbauer
reviewed
May 30, 2019
HansMuller
reviewed
May 31, 2019
Contributor
HansMuller
left a comment
There was a problem hiding this comment.
I only reviewed _AnimatedFadeOutFadeIn; looks pretty good to me.
9 tasks
Contributor
Author
|
FYI, waiting for LGTM on this. I also submitted #33674 for review to address the documentation in |
tvolkert
added a commit
that referenced
this pull request
Jun 1, 2019
This is a follow-on to #33370 based on review comments therein.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This updates
FadeInImageto use the newImage.frameBuilderAPI (added in #33369), to greatly
simplify the implementation of
FadeInImage.This also removes the
FadeInImage.placeholderSemanticLabelproperty.This property was added in #28799 for the sake of completeness (the bug
it fixed was the lack of any semantic label support in FadeInImage), but a
placeholder is a transient visual artifact, not something that affects the
underlying semantic meaning of the image.
Related Issues
FadeInImage.placeholderSemanticLabelproperty #33480Tests
I added full test coverage of the two new properties (verified in merged
lcov.info). Due to the fact that the implementation ofFadeInImagewas completely rewritten, I replaced the existing tests with new tests that verify thatFadeInImage:Checklist
///).flutter analyze --flutter-repo) does not report any problems on my PR.Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?