Copy unawaited implementation into Ably Flutter to fix build failures for Flutter 2.2.3 #198
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A customer has asked us to add support for Flutter 2.2.3 to avoid them upgrading to Flutter 2.5 in a slack message. Unfortunately, currently, we are using
unawaitedintroduced in Dart 2.14, which is first available in Flutter 2.5.0.As a solution, we copied the 1 line of implementation into this SDK, and import this instead.
We are also planning to add tests using older Flutter versions in CI to avoid this problem in the future, but there are some challenges in doing so, which we will tackle in a separate (currently draft) PR: #197