Dart 2 invokeMethod compatibility

[xqwzts]

With the upcoming Dart 2 changes we will run into errors when returning anything other than Future<dynamic> from invokeMethod calls.

Calls like:

Future<bool> get isOn => _channel.invokeMethod('isOn');

Need to be updated to:

Future<bool> get isOn async {
 final bool isOn = await _channel.invokeMethod('isOn');
 return isOn;
}

More details in this issue: flutter/flutter#15654

[staadecker]

Seems like this is not fully finished. The flutterBlue.isAvailable and flutter.isOn methods still throw errors

[staadecker]

I can submit a pull request but I need to know what is best practice (probably option 1).

Option 1
As @xqwzts recommands in his comment

Option 2
Simply change the return type from Future<bool> to Future

Thanks in advance!

[itavero]

I think this issue needs to be reopened, as I am still getting errors when using isOn or isAvailable in v0.4.0.

[staadecker]

After more thought I think option 1 (from @xqwzts) is better since it doesn't change the method signature. I will submit a pull request when I have a moment.

[staadecker]

I submitted a pull request to fix. See issue #122 and pull request #123