-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add timeout option #239
Add timeout option #239
Conversation
6da4931
to
2e0c943
Compare
2e0c943
to
82ce134
Compare
Since the test and actual fn definition are equal and HTTP is allowed in every case, the test function is not needed anymore
Resolves warnings when creating docs and therefore makes failure on warning possible
a65fa00
to
9d09d5b
Compare
I have pushed some commits that resolve warnings and added a job to run clippy linting to the CI pipeline. Furthermore, I disallowed warnings when they occur in the jobs. Please let me know if you want to have this as a separate PR. Be aware that I renamed the config |
Very nice! I like the new types, the weird hyper legacy client thing got on my nerves by now. I noticed that |
src/authenticator.rs
Outdated
@@ -988,7 +994,61 @@ pub type DefaultAuthenticator = | |||
yup_oauth2_docsrs, | |||
doc(cfg(any(feature = "hyper-rustls", feature = "hyper-tls"))) | |||
)] | |||
pub struct DefaultHyperClient; | |||
#[derive(Default)] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe move this to the client
module as well? It looks general enough to make sense there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
True! I moved the DefaultHyperClient
as well as the CustomHyperClient
to the client
module and appended Builder
to them.
65dea01
to
ef846b6
Compare
ef846b6
to
ff1ffe9
Compare
8b08db7
to
0d7dad9
Compare
0d7dad9
to
d61b4cb
Compare
Adds the option to add a timeout after which a request will fail. PR #238 should be reviewed before this