remove Layer.replaceWith due to no usage and no tests#33164
Merged
Conversation
goderbauer
added
the
framework
Piinks
reviewed
May 23, 2019
Piinks
left a comment
Piinks
left a comment
Contributor
There was a problem hiding this comment.
Looks ok to me pending feedback from the breaking change announcement.
Contributor
Author
|
It's been 2 days since the breaking change announcement. The feedback is a deafening silence :) What do we do in this case? |
Contributor
|
Silence is approval. LGTM. |
Contributor
Author
|
I was waiting for the build to go green. Yep. Submitting. Thanks! |
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.
5 participants
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
Remove Layer.replaceWith.
Related Issues
Fixes #33015
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]). This will ensure a smooth and quick review process.///).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?