Rearrange the where clause for generated Client::new() constructors #26
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.
This PR rearranges the where clause on
Client::new()
to make it work with type inference andimpl Trait
better.Clients currently explicitly require that an
auth
can be turned into aBox<dyn GetAccessToken>
, but this doesn't play well withimpl Trait
and theimpl GetAccessToken
returned bygoogle_api_auth::yup_oauth2::from_authenticator()
.For example, I am trying to use the following code:
(original code)
And
rustc
fails with the unhelpful error message "the trait boundimpl google_api_auth::GetAccessToken: std::convert::From<impl google_api_auth::GetAccessToken>
is not satisfied"... Which doesn't make sense consideringT: From<T>
.This is linked to #24 in that the user experience for authentication isn't great.