Martin Kustermann
Martin Kustermann
> I think with inline class we could even consider going all in and making Int64 an unboxed value. It's going to be a breaking change but much smaller one...
/cc @sigurdm @jonasfj Could you find an appropriate area label?
Uploaded https://github.com/dart-lang/test/pull/2233
CL is up for review: https://codereview.chromium.org/775993002/
So currently the following snippet would be necessary: ``` dart chrome.identity.getAuthToken().then((token) { var client = new http.Client(); var expiryDate = ???; var accessToken = new AccessToken('Bearer', token, expiryDate); var accessCredentials...
It's in [`package:http/browesr_client.dart`](http://www.dartdocs.org/documentation/http/0.11.1+1/index.html#http/http-browser_client.BrowserClient). So don't use `new http.Client()` but rather `new BrowserClient()` :)
I've merged the PR. @Scarygami Thanks for adding the tests :) I agree that the current implementation is not so ideal. Though, I don't really want to add a `code`...
I've published the new version on pub.
Could you describe how you created the client Id in the developers console?
I think we can turn the assertion into a check and an exception. Although we can never know why the server did not return a refresh token, we could hint...