Not an issue - you don't need to return await

[avioli]

You don't need to return await ...:

dart-rest-data/lib/src/adapters/mixins/http.dart

Lines 56 to 64 in ee58d83

	Future<http.Response> httpGet(
	String path, {
	Map<String, String> queryParams,
	}) async {
	return await _safelyRun(() async {
	var url = Uri.https(hostname, path, queryParams);
	return await http.get(url, headers: headers);
	});
	}

Which could be safely rewritten to:

 Future<http.Response> httpGet( 
   String path, { 
   Map<String, String> queryParams, 
 }) { 
   return _safelyRun(() { 
     final url = Uri.https(hostname, path, queryParams); 
     return http.get(url, headers: headers); 
   }); 
 } 

The future chain will await by itself.

You only need to when in a try/catch block, since you need to get the future to resolve within your scope:

dart-rest-data/lib/src/adapters/mixins/http.dart

Lines 94 to 104 in ee58d83

	Future<http.Response> _safelyRun(Future<http.Response> method()) async {
	try {
	return await method();
	} on SocketException {
	throw NoNetworkError();
	} on http.ClientException {
	throw NetworkError();
	} on TlsException {
	throw NetworkError();
	}
	}

[safeforge]

Sorry @avioli, this really went out of my radar - can you create a PR?

Thank you!

[avioli]

#16