Chris Broadfoot
Chris Broadfoot
/cc @bradfitz if he has an opinion about this. etags are the most prevalent use of this type, and I'd hope that most usage is pretty opaque: pseudocode: ``` o...
@jadekler +1 Two options to improve this without making a breaking change: * improved docs/examples * getters/setters (or combination/both) More generally, maybe we should collect these types of issues under...
@wyuan1704 are you referring to if you had used ```go c := s.Method() c.Header().Set("User-Agent", "...") resp, err := c.Do() ``` ?
It sounds like we should simply swap the order to match the spec. Also, some more ideas here: #494
Another pattern you might want to look at is to encrypt the key JSON and pass along the secrets in environment variables. You'd need to decrypt the file on application...
Hi folks, an update on this feature request. We won't be implementing this any time soon, but it's on our list of ideas for improvements to our auth libraries.
+1, would love to see ability to create a driver.Connector from a net.Conn. The caller can set up tls if necessary.
-1 to "token" but +1 to a function or something that provides a token (a promise, since it often involves a network request, e.g. to refresh), so that it can...
What do you do after the token has expired? In most cases, you don't actually want a static token, rather some token source that will always provide a valid token,...
+1, this is certainly a problem (there's many problems with this package that I won't go into) and +1 to #262, Token() should take a ctx, for sure. However, it...