This repository has been archived by the owner on Feb 22, 2023. It is now read-only.
[webview_flutter] Remove the upper bound from the Flutter SDK constraint #2517
Conversation
This file contains 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
stuartmorgan
approved these changes
Feb 11, 2020
sanekyy
pushed a commit
to sanekyy/plugins
that referenced
this pull request
Feb 18, 2020
…int (flutter#2517) As the Flutter SDK does not follow semver, an upper bound has no semantic meaning. Using this plugin as a canary to check if anything breaks when we remove this bound.
EdwinRomelta
pushed a commit
to EdwinRomelta/plugins
that referenced
this pull request
Jun 11, 2020
…int (flutter#2517) As the Flutter SDK does not follow semver, an upper bound has no semantic meaning. Using this plugin as a canary to check if anything breaks when we remove this bound.
FlutterSu
pushed a commit
to FlutterSu/flutter-plugins
that referenced
this pull request
Nov 20, 2020
…int (flutter#2517) As the Flutter SDK does not follow semver, an upper bound has no semantic meaning. Using this plugin as a canary to check if anything breaks when we remove this bound.
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
As the Flutter SDK does not follow semver, an upper bound has no semantic meaning.
Using this plugin as a canary to check if anything breaks when we remove this bound.