Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@joates-mobilus
Copy link
Contributor

Because the return value of start is void rather than Future it is impossible to await it's completion because it has been flagged as async.

Users choosing to allow the call to be completed asynchronously can simply ignore the Future but those wanting to act after registration is complete cannot do so without this change.

Because the return value of start is void rather than Future<void> it is impossible to await it's completion because it has been flagged as async.

Users choosing to allow the call to be completed asynchronously can simply ignore the Future<void> but those wanting to act after registration is complete cannot do so without this change.
Copy link
Collaborator

@Perondas Perondas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Perondas
Copy link
Collaborator

Only saw this after doing the new release, I'll get it in with the next version.

@Perondas Perondas merged commit 809f50c into flutter-webrtc:master May 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants