You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 27, 2022. It is now read-only.
Hi! I'd like to have an option to customize the reqwest::Client for explicit proxy setup, and thought that it might be a good time to add a builder for the Client fields. And while I'm at it, changing Client::credentials to be somehow optional (either through an Option or turning it into enum) would be great as well, as I'm currently just passing empty strings for the credential values and it seems wrong :) Unfortunately it's not backwards-compatible change. What do you think?
The text was updated successfully, but these errors were encountered:
I like the ClientBuilder idea! I'll implement that.
I don't want to make credentials an Option or an enum because for most use cases, it's not optional. I'm starting to think that a TokenSource trait would be the best option.
I like the ClientBuilder idea! I'll implement that.
I'm actually on it already! I'll push a writable PR.
I don't want to make credentials an Option or an enum because for most use cases, it's not optional. I'm starting to think that a TokenSource trait would be the best option.
Hi! I'd like to have an option to customize the
reqwest::Client
for explicit proxy setup, and thought that it might be a good time to add a builder for theClient
fields. And while I'm at it, changingClient::credentials
to be somehow optional (either through anOption
or turning it intoenum
) would be great as well, as I'm currently just passing empty strings for the credential values and it seems wrong :) Unfortunately it's not backwards-compatible change. What do you think?The text was updated successfully, but these errors were encountered: